[Bug testsuite/25728] File descriptor leak in lib/gcov.exp

2006-01-11 Thread hjl at lucon dot org
--- Comment #6 from hjl at lucon dot org 2006-01-12 01:47 --- Fixed. -- hjl at lucon dot org changed: What|Removed |Added Status|UNCONFIRMED |

[Bug target/24959] Trampolines fail on i686-apple-darwin because stack is not executable

2006-01-11 Thread pinskia at gcc dot gnu dot org
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-01-12 01:56 --- gcc.c-torture/execute/2822-1.c fails the same way. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24959

[Bug target/24959] Trampolines fail on i686-apple-darwin because stack is not executable

2006-01-11 Thread pinskia at gcc dot gnu dot org
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-01-12 01:57 --- I will submit this. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Assigne

[Bug libstdc++/25191] exception_defines.h #defines try/catch

2006-01-11 Thread hhinnant at apple dot com
--- Comment #33 from hhinnant at apple dot com 2006-01-12 02:49 --- (In reply to comment #32) > As I said before, there is still a diagnostic issue and now it is worse > with > doing that in the front-end since people don't read docs that well so > we will > be getting bug reports abou

[Bug target/25758] New: gcc.c-torture/compile/20030921-1.c fails at -O0

2006-01-11 Thread pinskia at gcc dot gnu dot org
The fix is: Index: i386.c === --- i386.c (revision 109602) +++ i386.c (working copy) @@ -6680,6 +6682,8 @@ output_pic_addr_const (FILE *file, rtx x break; case SYMBOL_REF: + if (SYMBOL_REF_DECL (x)) +

[Bug fortran/25062] same name for parameter and common block

2006-01-11 Thread kargl at gcc dot gnu dot org
--- Comment #7 from kargl at gcc dot gnu dot org 2006-01-12 05:25 --- See 14.1.2.1. A common block name in a scoping unit also may be the name of any local entity other than a named constant, intrinsic procedure, or a local variable that is also an external function in a functio

[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2006-01-12 06:46 --- This is interesting. I noticed before that with the previous test case i could get two different error message depending on the size of the data. I will have to study this a bit closer. BTW Thanks for the test

<    1   2