[Bug c++/54498] New: incorrect code generation from g++ -O on x86_64

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54498 Bug #: 54498 Summary: incorrect code generation from g++ -O on x86_64 Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRMED Severity: normal

[Bug fortran/49501] support ATTRIBUTES ALIGN in gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49501 --- Comment #1 from stevenj at alum dot mit.edu 2011-06-22 17:38:25 UTC --- Actually, it looks like there is a way to allocate aligned memory, albeit a bit ugly, thanks to Fortran 2003's C interoperability. Declare a bind(C) interface to e.g

[Bug fortran/49509] New: cannot promote types for arguments passed by value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49509 Summary: cannot promote types for arguments passed by value Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran

[Bug fortran/49509] cannot promote types for arguments passed by value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49509 --- Comment #3 from stevenj at alum dot mit.edu 2011-06-23 03:00:47 UTC --- Hence, the familiar old requirements of the Fortran standard are irrelevant. The question is, what does the Fortran 2003 standard require for passing by value, which

[Bug fortran/49509] cannot promote types for arguments passed by value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49509 --- Comment #2 from stevenj at alum dot mit.edu 2011-06-23 02:54:50 UTC --- You're missing the point. Traditionally in Fortran, all arguments were passed *by reference*, in which case it is clearly a requirement that actual parameter match

[Bug fortran/49509] cannot promote types for arguments passed by value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49509 --- Comment #4 from stevenj at alum dot mit.edu 2011-06-23 03:23:06 UTC --- Section 12.4.1.2 of Fortran 2003 standard: If the dummy argument has the VALUE attribute it becomes associated with a definable anonymous data object whose initial value

[Bug fortran/49501] New: support ATTRIBUTES ALIGN in gfortran

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49501 Summary: support ATTRIBUTES ALIGN in gfortran Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: fortran AssignedTo:

[Bug fortran/41209] Add full ATTRIBUTE support to gfortran (ALIGN, (WEAK)ALIAS, ...)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41209 stevenj at alum dot mit.edu changed: What|Removed |Added CC||stevenj at alum dot mit.edu

[Bug c/48956] -Wconversion should warn when a complex value is assigned to a real result

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48956 --- Comment #6 from stevenj at alum dot mit.edu 2011-05-12 22:33:59 UTC --- Thanks, I was somewhat aware of the additional requirements for applying patches to the official tree (probably I should also file a copyright assignment), but I wanted

[Bug c/48956] -Wconversion should warn when a complex value is assigned to a real result

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48956 --- Comment #4 from stevenj at alum dot mit.edu 2011-05-11 20:16:57 UTC --- Created attachment 24230 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=24230 patch to add a -Wconversion warning for complex - real conversions I believe

[Bug c/48956] -Wconversion should warn when a complex value is assigned to a real result

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48956 --- Comment #1 from stevenj at alum dot mit.edu 2011-05-11 00:01:32 UTC --- PPS. I have reproduced this problem in gcc versions 3.3.6, 3.4.6, 4.1.3, 4.3.2, and 4.6.0 running on an x86_64 Debian GNU/Linux system.

[Bug c/48956] New: -Wconversion should warn when a complex value is assigned to a real result

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48956 Summary: -Wconversion should warn when a complex value is assigned to a real result Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug rtl-optimization/29874] gcc-4.1.1 generates consistently worse performming SSE code than gcc-3.4.6

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29874 --- Comment #2 from stevenj at alum dot mit.edu 2011-03-07 23:13:41 UTC --- Created attachment 23579 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=23579 benchmark extracted from FFTW3 - size 64 FFT with SSE2 I extracted a little benchmark