[Bug middle-end/19988] [4.0/4.1/4.2/4.3 Regression] pessimizes fp multiply-add/subtract combo

2007-07-31 Thread stevenj at alum dot mit dot edu
--- Comment #11 from stevenj at alum dot mit dot edu 2007-08-01 01:01 --- Given that there seems to be no progress, or even any prospect of progress, on Roger's "un-CSE" suggestion, isn't there a simpler fix? The basic issue here seems to be the abovementio

[Bug fortran/24261] gfortran ALLOCATE statement does not align objects on 16-byte boundary

2007-02-01 Thread stevenj at alum dot mit dot edu
--- Comment #7 from stevenj at alum dot mit dot edu 2007-02-02 02:06 --- > Well the C standard mentions there can be non standard integer types so that > exists for x86_64, __int128_t which has normally aligned 16bytes so again this > is a bug in glibc. First, 16-byte alig

[Bug fortran/24261] gfortran ALLOCATE statement does not align objects on 16-byte boundary

2007-02-01 Thread stevenj at alum dot mit dot edu
--- Comment #5 from stevenj at alum dot mit dot edu 2007-02-01 23:00 --- (In reply to comment #4) > This is really a glibc bug and needs to be fixed. The C standard says that > malloc allocates that the right alignment so this is a glibc bug. The C standard does not cove

[Bug other/24845] [gomp] make "-fopenmp" imply "-lgomp" when linking

2006-01-24 Thread stevenj at alum dot mit dot edu
--- Comment #4 from stevenj at alum dot mit dot edu 2006-01-24 23:41 --- The documentation apparently still needs to be fixed, as it currently (as of 20060117) says: "To generate the final exectuable, the runtime library @code{libgomp} must be linked in using @option{-

[Bug libfortran/20179] cannot mix C and Fortran I/O

2005-05-25 Thread stevenj at alum dot mit dot edu
--- Additional Comments From stevenj at alum dot mit dot edu 2005-05-25 16:47 --- It was already noted above that adding fflush to the user's code would fix the output. As a quality-of-implementation issue, however, I would suggest that libgfortran should do it. 1) Interoperating

[Bug libfortran/20179] cannot mix C and Fortran I/O

2005-05-24 Thread stevenj at alum dot mit dot edu
--- Additional Comments From stevenj at alum dot mit dot edu 2005-05-24 23:51 --- I doubt that merely omitting close() from the end of the library will entirely fix the problem. You really need to add an fflush before every output to stdio. For example, modify ciotst.f to

[Bug target/20272] AltiVec vector instructions fail unless compiled with -force_cpusubtype_ALL

2005-03-01 Thread stevenj at alum dot mit dot edu
--- Additional Comments From stevenj at alum dot mit dot edu 2005-03-02 04:16 --- (In reply to comment #2) > You need at least cctools 528.5 to have this work correctly. Ah, thanks, I just saw http://gcc.gnu.org/ml/gcc-patches/2004-10/msg01222.html ...yes, when I install cctools 52

[Bug c/20272] AltiVec vector instructions fail unless compiled with -force_cpusubtype_ALL

2005-03-01 Thread stevenj at alum dot mit dot edu
--- Additional Comments From stevenj at alum dot mit dot edu 2005-03-02 01:43 --- Created an attachment (id=8308) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8308&action=view) preprocessed test case the test case's preprocessed source doesn't seem to be showi