This is the mail archive of the
mailing list for the GCC project.
Re: [patch, libgfortran] PR44953 FAIL: gfortran.dg/char4_iunit_1.f03 * execution test
- From: Jerry DeLisle <jvdelisle at verizon dot net>
- To: Tobias Burnus <tobias dot burnus at physik dot fu-berlin dot de>
- Cc: fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Mon, 19 Jul 2010 06:19:20 -0700
- Subject: Re: [patch, libgfortran] PR44953 FAIL: gfortran.dg/char4_iunit_1.f03 * execution test
- References: <20100719124458.GA2542@physik.fu-berlin.de>
On 07/19/2010 05:44 AM, Tobias Burnus wrote:
Jerry DeLisle wrote:
The failures were due to some sloppy pointer use and I missed a few of
the functions in write.c during initial implementation. The attached
patch cleans this all up. New test cases are not needed.
Passed regression testing on IBM Power 5 running Linux and
Dominique reports success with the original test cases. Also
regression tested on x86-64-linux-gnu.
OK for trunk?
OK. Thanks for the patch!
Committed revision 162304.
Is PR 37077 now actually fixed or are there any other wide-char related
bugs?* If not, what's next on your agenda (besides white-space fixes)?
This should close 37077 and 44953.
I will have a look at the below wide-char source issue as well as the bugs
currently assigned to me.
Thanks for review.
(* Some FE+libcpp issue is that using wide chars in the source file does
not work work. In principle, a (e.g.) UTF-8 wide char in .f90 should
work for 4_'...' but it currently does not. As this works for C/C++, one
should check what one does there. Cf. -finput-charset (c-family/c-opts.c,
OPT_finput_charset_), -fexec-charset and -fwide-exec-charset. gfortran's
scanner.c already has some wide-char support.)