[Bug bootstrap/23131] [4.1 Regression] Fixincludes on cross-build is scanning /usr/include

2005-07-30 Thread cvs-commit at gcc dot gnu dot org

--- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-07-30 
08:07 ---
Subject: Bug 23131

CVSROOT:/cvs/gcc
Module name:gcc
Branch: csl-gxxpro-3_4-branch
Changes by: [EMAIL PROTECTED]   2005-07-30 08:06:54

Modified files:
.  : ChangeLog.csl 
gcc: configure.ac configure 

Log message:
PR bootstrap/23131
* configure.ac (SYSTEM_HEADER_DIR): Avoid setting to empty
string.
* configure: Regenerated.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/ChangeLog.csl.diff?cvsroot=gcc&only_with_tag=csl-gxxpro-3_4-branch&r1=1.1.10.1&r2=1.1.10.2
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/configure.ac.diff?cvsroot=gcc&only_with_tag=csl-gxxpro-3_4-branch&r1=2.19.2.13&r2=2.19.2.13.2.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/configure.diff?cvsroot=gcc&only_with_tag=csl-gxxpro-3_4-branch&r1=1.767.2.14&r2=1.767.2.14.2.1



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23131


[Bug tree-optimization/22416] [4.1 Regression] 23_containers/set/explicit_instantiation/1.cc fails: expected ssa_name, have var_decl in is_old_name, at tree-into-ssa.c:466

2005-07-30 Thread hp at gcc dot gnu dot org


-- 
Bug 22416 depends on bug 22444, which changed state.

Bug 22444 Summary: [4.1 regression] testsuite 
failure:23_containers/set/explicit_instantiation/2.cc ICE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22444

   What|Old Value   |New Value

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22416


[Bug tree-optimization/22444] [4.1 regression] testsuite failure:23_containers/set/explicit_instantiation/2.cc ICE

2005-07-30 Thread hp at gcc dot gnu dot org

--- Additional Comments From hp at gcc dot gnu dot org  2005-07-30 08:17 
---
I'm reopening this PR as the failure with mmix-knuth-mmixware and
LAST_UPDATED "Fri Jul 29 18:30:36 UTC 2005" is identical to the
original description.

-- 
   What|Removed |Added

 Status|RESOLVED|REOPENED
 GCC target triplet|cris-axis-linux-gnu |mmix-knuth-mmixware
 Resolution|FIXED   |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22444


[Bug tree-optimization/22483] [4.1 Regression] ICE : tree check: expected ssa_name, have var_decl in is_old_name, at tree-into-ssa.c:466

2005-07-30 Thread hp at gcc dot gnu dot org


-- 
Bug 22483 depends on bug 22444, which changed state.

Bug 22444 Summary: [4.1 regression] testsuite 
failure:23_containers/set/explicit_instantiation/2.cc ICE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22444

   What|Old Value   |New Value

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22483


[Bug fortran/23146] New: -Wuninitialized could be supported without -O

2005-07-30 Thread schnetter at aei dot mpg dot de
When I use -Wuninitialized without -O, gfortran says 
 
f951: warning: -Wuninitialized is not supported without -O 
 
This is with 
 
GNU Fortran 95 (GCC 4.1.0 20050727 (experimental)) 
 
For debugging, I do not want optimisation, because this makes debugging more 
difficult.  On the other hand I do want warnings about uninitialised 
variables.

-- 
   Summary: -Wuninitialized could be supported without -O
   Product: gcc
   Version: 4.1.0
Status: UNCONFIRMED
  Severity: enhancement
  Priority: P2
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: schnetter at aei dot mpg dot de
CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23146


[Bug c++/23147] New: Missing declaration of static const members

2005-07-30 Thread fw at deneb dot enyo dot de
The program below compiles cleanly with GCC 4.0.1, although the definition of
Foo::foo required by the standard (9.4.2/4) is missing.

It probably makes sense to accept such programs as a GNU extension (as long as
the address of the member is not taken).

#include 

struct Foo
{
  static const int foo = 42;
};

int
main ()
{
  std::printf ("%d\n", Foo::foo);
  return 0;
}

-- 
   Summary: Missing declaration of static const members
   Product: gcc
   Version: 4.0.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: fw at deneb dot enyo dot de
CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23147


[Bug libfortran/23138] real-values print and add incorrectly (version 4.1.0 20050702, i686-pc-mingw32)

2005-07-30 Thread fxcoudert at gcc dot gnu dot org

--- Additional Comments From fxcoudert at gcc dot gnu dot org  2005-07-30 
10:56 ---
Marked as confirmed due to Jerry's comment. Right now, building on mingw is an 
awful pain (4 PR 
preventing the build), and cygwin is only a bit better. So, I think work on 
that point is useless until the 
situation gets clearer.

-- 
   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed||1
   Last reconfirmed|-00-00 00:00:00 |2005-07-30 10:56:59
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23138


[Bug c++/23147] Missing declaration of static const members

2005-07-30 Thread falk at debian dot org

--- Additional Comments From falk at debian dot org  2005-07-30 13:35 
---
Well, the behavior is undefined here, so what we currently do is just fine.

Moreover, this can only be detected at link time, so there's no way for us to
give a warning; at best, we could emit a fake reference and have the linker
hard fail. I don't think we want that, since it wastes space in the binary
for no really good reason other than being pedantic. So I'd say WONTFIX.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23147


[Bug c++/23147] Missing declaration of static const members

2005-07-30 Thread fw at deneb dot enyo dot de

--- Additional Comments From fw at deneb dot enyo dot de  2005-07-30 13:45 
---
What about a GNU extension which would make this program well-formed?  I think
it's quite a common pattern, and a requirement to provide a definition would
just increase object code size meaninglessly.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23147


[Bug middle-end/23146] -Wuninitialized could be supported without -O

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-30 
15:11 ---
-Wuninitialized is done in the back-end of GCC and not in the front-end.

And I think this was decided against so many times that there might be abother 
bug about this which 
has already been closed.

-- 
   What|Removed |Added

  Component|fortran |middle-end


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23146


[Bug c++/23147] Missing declaration of static const members

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-30 
15:13 ---
Actually the compiler is allowed to "inlined" the value of the constant.  And 
the missing definition does 
not have to be diagnostic.

So closing as invalid.

-- 
   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23147


[Bug middle-end/23146] -Wuninitialized could be supported without -O

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-30 
15:20 ---
This is a dup of 7710 but it is not going to be fixed because it is too hard to 
do and will make 
compile time way slower.

This has been discussed some many times but we are not going to do it.

*** This bug has been marked as a duplicate of 7710 ***

-- 
   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23146


[Bug c/7710] GCC warns " might be used uninitialized" when optimisation turned on

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-30 
15:20 ---
*** Bug 23146 has been marked as a duplicate of this bug. ***

-- 
   What|Removed |Added

 CC||schnetter at aei dot mpg dot
   ||de


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7710


[Bug libfortran/23138] real-values print and add incorrectly (version 4.1.0 20050702, i686-pc-mingw32)

2005-07-30 Thread pinskia at gcc dot gnu dot org


-- 
   What|Removed |Added

   Severity|critical|normal


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23138


[Bug debug/22514] [4.1 Regression] ICE in force_decl_die with invalid code after error

2005-07-30 Thread phython at gcc dot gnu dot org

--- Additional Comments From phython at gcc dot gnu dot org  2005-07-30 
15:25 ---
http://gcc.gnu.org/ml/gcc-patches/2005-07/msg02054.html

-- 
   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |phython at gcc dot gnu dot
   |dot org |org
 Status|NEW |ASSIGNED
   Keywords||patch
   Last reconfirmed|2005-07-16 19:47:35 |2005-07-30 15:25:06
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22514


[Bug c++/23139] [3.4/4.0/4.1 Regression] -pedantic -ffast-math breaks working code

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-30 
15:26 ---
3.4 produces a warning and not an error, maybe the warning became a pedwarn in 
4.0.0 but this 
should not produce a warning or an error at all.

For some reason the C front-end does not produce a warning or an error.

-- 
   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed||1
   Keywords||diagnostic
  Known to fail||3.4.0 4.0.0 4.1.0
  Known to work||3.3.3
   Last reconfirmed|-00-00 00:00:00 |2005-07-30 15:26:19
   date||
Summary|-pedantic -ffast-math breaks|[3.4/4.0/4.1 Regression] -
   |working code|pedantic -ffast-math breaks
   ||working code
   Target Milestone|--- |4.0.2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23139


[Bug rtl-optimization/23100] poor code generation for i686

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-30 
15:39 ---
Yes it is the same issue as PR 16796.

To reproduce this before 3.4.0, you have to add __attribute__((regparam(1))).  
Though the code is worse 
than before 3.3.3.

-- 
   What|Removed |Added

OtherBugsDependingO||16796
  nThis||
 Status|UNCONFIRMED |NEW
 Ever Confirmed||1
  Known to fail||3.4.0 4.0.0 4.1.0
   Last reconfirmed|-00-00 00:00:00 |2005-07-30 15:39:09
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23100


[Bug rtl-optimization/23100] poor code generation for i686

2005-07-30 Thread pinskia at gcc dot gnu dot org


-- 
   What|Removed |Added

   Severity|normal  |enhancement


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23100


[Bug tree-optimization/22598] [4.1 Regression] 23_containers/set/explicit_instantiation/3.cc fails

2005-07-30 Thread pinskia at gcc dot gnu dot org


-- 
   What|Removed |Added

OtherBugsDependingO||22444
  nThis||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22598


[Bug driver/21366] The -bundle linking option does not get processed right on darwin

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-30 
16:08 ---
Patches posted here:
http://gcc.gnu.org/ml/gcc-patches/2002-10/msg01961.html
and
http://gcc.gnu.org/ml/gcc-patches/2002-12/msg00655.html

I did not read through the whole thread to figure out what happened to the 
patch.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21366


[Bug tree-optimization/23128] [4.1 Regression] VRP fails for unsigned values

2005-07-30 Thread phython at gcc dot gnu dot org

--- Additional Comments From phython at gcc dot gnu dot org  2005-07-30 
18:12 ---
Created an attachment (id=9388)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9388&action=view)
Patch for a bunch of vrp problems


-- 
   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |phython at gcc dot gnu dot
   |dot org |org
 Status|NEW |ASSIGNED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23128


[Bug tree-optimization/23129] [4.1 Regression] VRP propagates division of antiranges incorrectly

2005-07-30 Thread phython at gcc dot gnu dot org

--- Additional Comments From phython at gcc dot gnu dot org  2005-07-30 
18:13 ---
 See the patch in pr23128.

-- 
   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |phython at gcc dot gnu dot
   |dot org |org
 Status|NEW |ASSIGNED
   Last reconfirmed|2005-07-29 11:08:52 |2005-07-30 18:13:45
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23129


[Bug target/20094] gcc.dg/transparent-union-* fail on ia64-hpux

2005-07-30 Thread jsm28 at gcc dot gnu dot org

--- Additional Comments From jsm28 at gcc dot gnu dot org  2005-07-30 19:19 
---
My newly added test transparent-union-4.c fails on ia64-hpux for the same 
reason.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20094


[Bug gcov/profile/23148] New: [4.1 Regression] gcov test failures

2005-07-30 Thread jsm28 at gcc dot gnu dot org
FAIL: 102:is -:should be 1
FAIL: 258: expected branch percentages not found: 25
FAIL: g++.dg/gcov/gcov-1.C gcov: 1 failures in line counts, 1 in branch
percentages, 0 in return percentages
FAIL: 211: expected branch percentages not found: 25
FAIL: 96:is -:should be 1
FAIL: gcc.misc-tests/gcov-4.c gcov: 1 failures in line counts, 0 in branch
percentages, 0 in return percentages
FAIL: gcc.misc-tests/gcov-4b.c gcov: 0 failures in line counts, 1 in branch
percentages, 0 in return percentages

have appeared on mainline on 20050729 on multiple platforms.  This appears to be
a regression.  (I'll file a separate bug for the nonstandard format of those
FAIL lines.)

-- 
   Summary: [4.1 Regression] gcov test failures
   Product: gcc
   Version: 4.1.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: gcov/profile
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jsm28 at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23148


[Bug testsuite/23149] New: gcov test assertion naming

2005-07-30 Thread jsm28 at gcc dot gnu dot org
On 20050728 the results in gcc.sum for gcov-4.c said:

PASS: gcc.misc-tests/gcov-4.c (test for excess errors)
PASS: gcc.misc-tests/gcov-4.c execution test
PASS: gcc.misc-tests/gcov-4.c gcov

while on 20050730 with no change to the test they said:

PASS: gcc.misc-tests/gcov-4.c (test for excess errors)
PASS: gcc.misc-tests/gcov-4.c execution test
FAIL: 96:is -:should be 1
FAIL: gcc.misc-tests/gcov-4.c gcov: 1 failures in line counts, 0 in branch
percentages, 0 in return percentages

The text which appears after PASS or FAIL is meant to be a name for a test
assertion which is constant as long as the testcase itself is unchanged.  Thus a
testsuite regression should be indicated by PASS:  changing to FAIL:
 rather than by the removal of a PASS and its replacement by FAILs
with different names; new FAILs in general can indicate newly added tests which
fail from the start and may or may not be regressions.  (contrib/compare_tests
illustrates this logic, showing these new failures less helpfully than if the
PASS and FAIL lines had consistent test names, though it's not the tool I'm
actually using for this comparison.)

Thus, each gcov output line which is checked should have its own fixed test
assertion name which appears after PASS if the output is correct and after FAIL
if the output is incorrect; the .log file might have additional information
about what the difference was, but not on the PASS or FAIL lines.  The final
summary PASS or FAIL line probably isn't needed in these circumstances, but if
it is again the test assertion name should not depend on whether the test passes
or fails (information about the number and kind of failures is a separate
matter, not for the PASS or FAIL lines).

-- 
   Summary: gcov test assertion naming
   Product: gcc
   Version: 4.1.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: testsuite
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jsm28 at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23149


[Bug tree-optimization/21831] [4.1 Regression] gcc.dg/vect/vect-97.c fails

2005-07-30 Thread jsm28 at gcc dot gnu dot org

--- Additional Comments From jsm28 at gcc dot gnu dot org  2005-07-30 19:50 
---
Started passing again on ia64-hpux between 20050708 and 20050711, I don't know
about on the other platforms discussed.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21831


[Bug target/23150] New: 20050713-1.c fails on arm-none-eabi with -O2 or -Os.

2005-07-30 Thread kazu at gcc dot gnu dot org
Here is a reduced version of 20050713-1.c.

extern void abort (void);

struct S
{
  int a, b, c;
};

int
foo2 (struct S x, struct S y)
{
  if (x.b != 4)
abort ();
  return 0;
}

int
bar2 (struct S x, struct S y)
{
  return foo2 (y, x);
}

int
main (void)
{
  struct S a = { 3, 4, 5 }, b = { 6, 7, 8 };

  bar2 (b, a);
  return 0;
}

Unlike PR 23090, which is for powerpc and only about -O2,
this one fails with -O2 or -Os on arm-none-eabi.

Since I have not analyzed the failure, I cannot conclude that
this is a duplicate of PR 23090 yet.

-- 
   Summary: 20050713-1.c fails on arm-none-eabi with -O2 or -Os.
   Product: gcc
   Version: unknown
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: kazu at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: arm-none-eabi


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23150


[Bug fortran/23151] New: print (buf, format), expression should be invalid

2005-07-30 Thread tkoenig at gcc dot gnu dot org
The following is illegal:

$ cat print.f90
program main
  character*80 line
  print (line,'(A)'), 'hello'
end program main
$ cat print.f90
program main
  character*80 line
  print (line,'(A)'), 'hello'
end program main
$ gfortran print.f90
$ gfortran -std=f95 print.f90
$ gfortran -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.1/configure --prefix=/home/ig25
--enable-languages=c,f95 : (reconfigured) ../gcc-4.1/configure
--prefix=/home/ig25 --enable-languages=c,f95
Thread model: posix
gcc version 4.1.0 20050726 (experimental)

-- 
   Summary: print (buf, format), expression should be invalid
   Product: gcc
   Version: unknown
Status: UNCONFIRMED
  Keywords: accepts-invalid, diagnostic
  Severity: normal
  Priority: P2
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: tkoenig at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23151


[Bug target/23150] 20050713-1.c fails on arm-none-eabi with -O2 or -Os.

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-30 
20:40 ---
(In reply to comment #0)
> Unlike PR 23090, which is for powerpc and only about -O2,
> this one fails with -O2 or -Os on arm-none-eabi.

You mean only about -Os.

You might want to check if this is a regression.  I would think it is a 
regression from 3.4.0.

-- 
   What|Removed |Added

   Keywords||wrong-code


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23150


[Bug libfortran/22436] print *,tiny(1._10) yields asterisks

2005-07-30 Thread cvs-commit at gcc dot gnu dot org

--- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-07-30 
20:45 ---
Subject: Bug 22436

CVSROOT:/cvs/gcc
Module name:gcc
Changes by: [EMAIL PROTECTED]   2005-07-30 20:45:03

Modified files:
libgfortran: ChangeLog 
libgfortran/io : write.c 

Log message:
PR libfortran/22436
* io/write.c (write_real): Add default formats for real(10) and
real(16).

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&r1=1.272&r2=1.273
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/write.c.diff?cvsroot=gcc&r1=1.44&r2=1.45



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22436


[Bug libfortran/22436] print *,tiny(1._10) yields asterisks

2005-07-30 Thread fxcoudert at gcc dot gnu dot org

--- Additional Comments From fxcoudert at gcc dot gnu dot org  2005-07-30 
20:47 ---
Fixed on mainline. 4.0 branch does not have support for large real kinds, so no 
need to apply there.

-- 
   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution||FIXED
   Target Milestone|--- |4.1.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22436


[Bug libfortran/22143] missing kinds 1 and 2 for eoshift and cshift

2005-07-30 Thread fxcoudert at gcc dot gnu dot org

--- Additional Comments From fxcoudert at gcc dot gnu dot org  2005-07-30 
20:59 ---
Thomas, I guess your patch is doing the right thing. Could you submit it to gcc-
patches so that it gets reviewed?

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22143


[Bug libfortran/21787] flush I/O before calling abort()

2005-07-30 Thread fxcoudert at gcc dot gnu dot org

--- Additional Comments From fxcoudert at gcc dot gnu dot org  2005-07-30 
21:18 ---
For the bug noted in comments 5 and 6:

[dranta:~/tests/gfortran] dir% gfortran -o callabort callabort.f
[dranta:~/tests/gfortran] dir% callabort
Abort
[dranta:~/tests/gfortran] dir% cat callabort.f
  program test
  write(3,*)' error in program'
  call abort
  end
[dranta:~/tests/gfortran] dir% cat fort.3
[dranta:~/tests/gfortran] dir% 

A fix is easy to design: calling close_units() before abort() in file 
intrinsics/abort.c does the trick (no time to submit a real patch now, just 
noting this in case I forget about it).

-- 
   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |fxcoudert at gcc dot gnu dot
   |dot org |org
 Status|NEW |ASSIGNED
   Keywords||patch
   Last reconfirmed|2005-06-02 13:40:54 |2005-07-30 21:18:15
   date||
Summary|libfortran - better error   |flush I/O before calling
   |message needed  |abort()


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21787


[Bug tree-optimization/22538] Does not remove stores for struct assignments

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-30 
21:46 ---
Confirmed.

-- 
   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed||1
   Last reconfirmed|-00-00 00:00:00 |2005-07-30 21:46:41
   date||
Summary|Eustore does not remove |Does not remove stores for
   |stores for struct   |struct assignments
   |assignments |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22538


[Bug libfortran/20436] [4.0 only] using nested reshape functions gives runtime error

2005-07-30 Thread cvs-commit at gcc dot gnu dot org

--- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-07-30 
22:29 ---
Subject: Bug 20436

CVSROOT:/cvs/gcc
Module name:gcc
Branch: gcc-4_0-branch
Changes by: [EMAIL PROTECTED]   2005-07-30 22:29:25

Modified files:
gcc/testsuite  : ChangeLog 
Added files:
gcc/testsuite/gfortran.dg: nested_reshape.f90 reshape-alloc.f90 
   reshape.f90 

Log message:
2005-07-30  Thomas Koenig  <[EMAIL PROTECTED]>

Backport from mainline:
PR libfortran/20074
PR libfortran/20436
PR libfortran/21108
* gfortran.dg/nested_reshape.f90:  Actually commit.
* gfortran.dg/reshape-alloc.f90:  Actually commit.
* gfortran.dg/reshape.f90:  Actually commit.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.5084.2.311&r2=1.5084.2.312
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/nested_reshape.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.14.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/reshape-alloc.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.14.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/reshape.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.14.1



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20436


[Bug libfortran/20074] [4.0 only] reshape of pointer array segfaults at runtime

2005-07-30 Thread cvs-commit at gcc dot gnu dot org

--- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-07-30 
22:29 ---
Subject: Bug 20074

CVSROOT:/cvs/gcc
Module name:gcc
Branch: gcc-4_0-branch
Changes by: [EMAIL PROTECTED]   2005-07-30 22:29:25

Modified files:
gcc/testsuite  : ChangeLog 
Added files:
gcc/testsuite/gfortran.dg: nested_reshape.f90 reshape-alloc.f90 
   reshape.f90 

Log message:
2005-07-30  Thomas Koenig  <[EMAIL PROTECTED]>

Backport from mainline:
PR libfortran/20074
PR libfortran/20436
PR libfortran/21108
* gfortran.dg/nested_reshape.f90:  Actually commit.
* gfortran.dg/reshape-alloc.f90:  Actually commit.
* gfortran.dg/reshape.f90:  Actually commit.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.5084.2.311&r2=1.5084.2.312
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/nested_reshape.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.14.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/reshape-alloc.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.14.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/reshape.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.14.1



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20074


[Bug libfortran/21108] [4.0 only] reshape with order causes random results

2005-07-30 Thread cvs-commit at gcc dot gnu dot org

--- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-07-30 
22:29 ---
Subject: Bug 21108

CVSROOT:/cvs/gcc
Module name:gcc
Branch: gcc-4_0-branch
Changes by: [EMAIL PROTECTED]   2005-07-30 22:29:25

Modified files:
gcc/testsuite  : ChangeLog 
Added files:
gcc/testsuite/gfortran.dg: nested_reshape.f90 reshape-alloc.f90 
   reshape.f90 

Log message:
2005-07-30  Thomas Koenig  <[EMAIL PROTECTED]>

Backport from mainline:
PR libfortran/20074
PR libfortran/20436
PR libfortran/21108
* gfortran.dg/nested_reshape.f90:  Actually commit.
* gfortran.dg/reshape-alloc.f90:  Actually commit.
* gfortran.dg/reshape.f90:  Actually commit.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.5084.2.311&r2=1.5084.2.312
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/nested_reshape.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.14.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/reshape-alloc.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.14.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/reshape.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.14.1



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21108


[Bug fortran/23152] New: namelist can't contain an assumed size array

2005-07-30 Thread tkoenig at gcc dot gnu dot org
The following should be illegal:

$ cat namelist-1.f90
program main
  integer, dimension(2) :: i
  i = 2
  call foo(i)
contains
  subroutine foo(i)
integer :: i(:)
namelist /bar/ i
write (*,bar)
  end subroutine foo
end program main
$ gfortran namelist-1.f90
$ gfortran -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.1/configure --prefix=/home/ig25
--enable-languages=c,f95 : (reconfigured) ../gcc-4.1/configure
--prefix=/home/ig25 --enable-languages=c,f95
Thread model: posix
gcc version 4.1.0 20050726 (experimental)

This is actually a testcase in gfortran.dg/namelist_14.f90 ,
which would need to be fixed.

-- 
   Summary: namelist can't contain an assumed size array
   Product: gcc
   Version: unknown
Status: UNCONFIRMED
  Keywords: accepts-invalid, diagnostic
  Severity: normal
  Priority: P2
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: tkoenig at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23152


[Bug rtl-optimization/23153] New: code size regression from 4.0 on x86

2005-07-30 Thread dann at godzilla dot ics dot uci dot edu
Compiling xterm-202 on i686-pc-linux-gnu shows that 4.1 generates bigger code
than 4.0. 
This happens for all combinations of {-march=i386 and -march=i686} and 
{-O2 and -Os}. 

 size -f 4.*/xterm
  textdata bss dec hex filename
 175215   217246684  203623   31b67 4.0-O2-i386/xterm
 181835   140526684  202571   3174b 4.1-O2-i386/xterm
 189064   217286684  217476   35184 4.0-O2-i686/xterm
 195680   140566684  216420   34d64 4.1-O2-i686/xterm
 148727   217246684  177135   2b3ef 4.0-Os-i386/xterm
 156443   140526684  177179   2b41b 4.1-Os-i386/xterm
 149011   217246684  177419   2b50b 4.0-Os-i686/xterm
 156779   140526684  177515   2b56b 4.1-Os-i686/xterm

The same is true for the individual object files, not only for the final 
binary. 
The preprocessed sources can be obtained from PR22574

If someone wants to investigate the cause, maybe it would be a good idea to look
at one of the small files like xstrings.i (500 bytes text size).

-- 
   Summary: code size regression from 4.0 on x86
   Product: gcc
   Version: 4.1.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: rtl-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dann at godzilla dot ics dot uci dot edu
CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23153


[Bug rtl-optimization/23153] code size regression from 4.0 on x86

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-30 
23:13 ---
This could be many things, first we don't care about code size for -O2.

Second this is most likely jump threading.

Can you add -ftree-dominator-opts and see what the code size problems are?

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23153


[Bug middle-end/22380] [4.1 Regression] stack usage of g++.dg/opt/inline4.C increased (GC with blocks)

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
00:11 ---
Hmm, we leak all the BLOCKs created by the tree-inline:
tree-inline.c:421 (remap_block)   0: 0.0%  0: 
0.0%3166956:74.8%  0: 0.0%  
60903
tree-inline.c:2027 (expand_call_inline)   0: 0.0%  0: 
0.0%  10452: 0.2%  0: 0.0%
201


that is with 200 instead of 250 so we don't get a seg fault in GC when 
collecting it for the last time.

-- 
   What|Removed |Added

 CC||hubicka at gcc dot gnu dot
   ||org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22380


[Bug middle-end/22380] [4.1 Regression] stack usage of g++.dg/opt/inline4.C increased (GC with blocks)

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
00:26 ---
I was wrong in comment #1 for saying this was caused by the early inliner.
This was caused by: "Copy debug info properly in the inliner":
http://gcc.gnu.org/ml/gcc-patches/2005-06/msg02022.html

What is happening is that we are getting more BLOCKS which seems to link to 
each other which is 
weird.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22380


[Bug target/21723] [4.0 Regression] ICE while building libgfortran

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
00:43 ---
Fixed.

-- 
   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21723


[Bug gcov/profile/23148] [4.1 Regression] gcov test failures

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
00:46 ---
Confirmed.

-- 
   What|Removed |Added

 CC||hubicka at gcc dot gnu dot
   ||org
 Status|UNCONFIRMED |NEW
 Ever Confirmed||1
   Last reconfirmed|-00-00 00:00:00 |2005-07-31 00:46:51
   date||
   Target Milestone|--- |4.1.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23148


[Bug libfortran/23138] real-values print and add incorrectly (version 4.1.0 20050702, i686-pc-mingw32)

2005-07-30 Thread dannysmith at users dot sourceforge dot net

--- Additional Comments From dannysmith at users dot sourceforge dot net  
2005-07-31 00:56 ---
This may be the problem:

In mk-kinds-h.sh:

case $largest_ctype in
  float) echo "#define GFC_REAL_LARGEST_FORMAT \"\"" ;;
  double) echo "#define GFC_REAL_LARGEST_FORMAT \"l\"" ;;
  "long double") echo "#define GFC_REAL_LARGEST_FORMAT \"L\"" ;;
  *) echo "$0: Unknown type" >&2 ; exit 1 ;;
esac



Although mingw supports long double math, the native msvcrt.dll runtime printf 
family does not. The 'L' format specifier is ignored and passing long doubles 
to printf doesn't work at all--the values are interptreted as doubles.  The 
same problem occurs in libstdc++ and the unsatisfacpory hack that mingw distros 
use is to cast long doubles to doubles before sending to snprintf. 

Danny


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23138


[Bug libfortran/23154] New: Bad floating point in formatted read

2005-07-30 Thread jvdelisle at gcc dot gnu dot org
The following test case results in a floating point read error.

  DOUBLE PRECISION XIN, YIN, ZIN, WIN, QIN
  CHARACTER*4 SID, RID, RID2, REN, IUP
  CHARACTER*5 A

  CHARACTER*132 COMLYN

  COMLYN = "abcd efgh jklmn  1.2345.678 21.765  2.34
 &  3.45xxWXYZ"

  PRINT *, COMLYN
  READ(COMLYN,'(12X,A4,1X,A4,1X,A5,3X,3F8.3,F6.2,F6.2,6X,A4)'
 &   ) IUP,REN,A,XIN,YIN,ZIN,QIN,WIN,SID
  STOP
  end

Possibly related to NIST formatted I/O and pr22570

-- 
   Summary: Bad floating point in formatted read
   Product: gcc
   Version: 4.1.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: libfortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jvdelisle at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
  GCC host triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23154


[Bug tree-optimization/23048] [4.1 Regression] ICE in get_loop_body with -O1 -ftree-vectorize on 4.1.x

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
02:24 ---
If I turn off copy prop, this passes.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23048


[Bug rtl-optimization/19627] if-conversion2 generates wrong code / crash on SH4

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
02:35 ---
Fixed in 4.0.0.

-- 
   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED
   Target Milestone|--- |4.0.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19627


[Bug middle-end/20396] TRULY_NOOP_TRUNCATION ignored

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
02:38 ---
Confirmed.

-- 
   What|Removed |Added

URL||http://gcc.gnu.org/ml/gcc-
   ||patches/2005-
   ||04/msg00883.html
 Status|UNCONFIRMED |NEW
 Ever Confirmed||1
   Last reconfirmed|-00-00 00:00:00 |2005-07-31 02:38:26
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20396


[Bug middle-end/23135] find_reloads_toplev -> find_reloads_subreg_address uses wrong reload type

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
02:43 ---
Confirmed.

-- 
   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed||1
   Last reconfirmed|-00-00 00:00:00 |2005-07-31 02:43:04
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23135


[Bug target/21984] [4.1 regression] ICE in reload while compiling __mulxc3

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
03:44 ---
Has this been fixed?

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21984


[Bug tree-optimization/22122] [4.1 Regression] -ftree-vectorize ICE get_loop_body, at cfgloop.c:819

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
03:47 ---
-fno-tree-copy-prop "fixes" the problem.

-- 
   What|Removed |Added

 CC||dnovillo at gcc dot gnu dot
   ||org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22122


[Bug tree-optimization/22122] [4.1 Regression] -ftree-vectorize ICE get_loop_body, at cfgloop.c:819

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
03:48 ---
This is a dup of bug 23048.

*** This bug has been marked as a duplicate of 23048 ***

-- 
   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22122


[Bug tree-optimization/23048] [4.1 Regression] ICE in get_loop_body with -O1 -ftree-vectorize on 4.1.x

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
03:48 ---
*** Bug 22122 has been marked as a duplicate of this bug. ***

-- 
   What|Removed |Added

 CC||marcus at jet dot franken
   ||dot de


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23048


[Bug tree-optimization/23048] [4.1 Regression] ICE in get_loop_body with -O1 -ftree-vectorize on 4.1.x

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
03:49 ---
Testcase from PR 22122:
void f(unsigned char *mem)
{
   int i;

   for(i=0;i<4;i++) {
 while(mem[i]==0) ;
   }
}

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23048


[Bug ada/22533] [4.1 regression] ada / raised STORAGE_ERROR : stack overflow (or erroneous memory access)

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
04:04 ---
I am no longer going to work on this.

-- 
   What|Removed |Added

 AssignedTo|pinskia at gcc dot gnu dot  |unassigned at gcc dot gnu
   |org |dot org
URL|http://gcc.gnu.org/ml/gcc-  |
   |patches/2005-   |
   |07/msg01327.html|
 Status|ASSIGNED|NEW
   Keywords|patch   |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22533


[Bug libstdc++/22205] [4.1 Regression] errors debug mode on aix

2005-07-30 Thread pinskia at gcc dot gnu dot org


-- 
   What|Removed |Added

 Status|WAITING |NEW
   Last reconfirmed|2005-06-27 21:59:14 |2005-07-31 04:06:12
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22205


[Bug middle-end/19305] internal error: Segmentation fault (magick-6.1.7/convert.c:2255)

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
04:14 ---
no Feedback in 3 months.

-- 
   What|Removed |Added

 Status|WAITING |RESOLVED
 Resolution||INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19305


[Bug ada/19381] ACATS c954a03 raises storage error at runtime on s390-linux

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
04:14 ---
I am going on a limb here and say this is fixed.

-- 
   What|Removed |Added

 Status|WAITING |RESOLVED
 Resolution||FIXED
   Target Milestone|--- |4.0.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19381


[Bug java/19586] gij exits with SIGABR

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
04:16 ---
I cannot reproduce this and this works for everyone else.

-- 
   What|Removed |Added

 Status|WAITING |RESOLVED
 Resolution||WORKSFORME


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19586


[Bug tree-optimization/23155] New: Gimplification failed for union cast

2005-07-30 Thread dje at gcc dot gnu dot org
I am not sure that the example is valid GCC-extended C, but GCC definitely
should not ICE with "gimplification failed".  The example is:

typedef short __attribute__((vector_size (16))) v8hi;
union vx {short f[8]; v8hi v;};

extern void bar1(v8hi);

void
foo5 (v8hi vec, short n)
{
  ((union vx) vec).f[5] = n;
  bar1 (foo.v);
}

This is either ice-on-valid or ice-on-invalid, but something is broken.

-- 
   Summary: Gimplification failed for union cast
   Product: gcc
   Version: 4.1.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: tree-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dje at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: *-*-*
  GCC host triplet: *-*-*
GCC target triplet: *-*-*


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23155


[Bug middle-end/23155] [4.0/4.1 Regression] Gimplification failed for union cast

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
04:21 ---
The front-end produces:
  {.v=vec}.f[5] = n;


-- 
   What|Removed |Added

 Status|UNCONFIRMED |NEW
  Component|tree-optimization   |middle-end
 Ever Confirmed||1
   Last reconfirmed|-00-00 00:00:00 |2005-07-31 04:21:21
   date||
Summary|Gimplification failed for   |[4.0/4.1 Regression]
   |union cast  |Gimplification failed for
   ||union cast
   Target Milestone|--- |4.0.2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23155


[Bug tree-optimization/23155] Gimplification failed for union cast

2005-07-30 Thread dje at gcc dot gnu dot org

--- Additional Comments From dje at gcc dot gnu dot org  2005-07-31 04:21 
---
Sorry, there was a typo in the previous example.  The correct example is:

typedef short __attribute__((vector_size (16))) v8hi;
union vx {short f[8]; v8hi v;};

extern void bar1(v8hi);

void
foo5 (v8hi vec, short n)
{
  ((union vx) vec).f[5] = n;
  bar1 (vec);
}

and the output is:

$ ./xgcc -B./ -O0 -S a.c
gimplification failed:
{.v=vec} 
unit size 
align 128 symtab 0 alias set -1
fields 
BLK file a.c line 2 size  unit size

align 16 offset_align 128
offset 
bit offset  context
 chain >
chain >
   
arg 0 
TI file a.c line 2 size  unit size

align 128 offset_align 128 offset  bit
offset  context >
value 
used TI file a.c line 7 size  unit size 

align 128 context  initial
 arg-type  chain
>>>
a.c: In function 'foo5':
a.c:9: internal compiler error: gimplification failed

-- 
   What|Removed |Added

  Component|middle-end  |tree-optimization
Summary|[4.0/4.1 Regression]|Gimplification failed for
   |Gimplification failed for   |union cast
   |union cast  |
   Target Milestone|4.0.2   |---


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23155


[Bug tree-optimization/23155] [4.0/4.1 Regression] Gimplification failed for union cast

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
04:23 ---
Here is another testcase:
union vx {short f[8]; int v;};
int vec;

void
foo5 (int vec)
{
  ((union vx) vec).f[5] = 1;
}

-- 
   What|Removed |Added

Summary|Gimplification failed for   |[4.0/4.1 Regression]
   |union cast  |Gimplification failed for
   ||union cast
   Target Milestone|--- |4.0.2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23155


[Bug middle-end/23155] [4.0/4.1 Regression] Gimplification failed for union cast

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
04:25 ---
If we give -pedantic-errors we reject it with an error but still ICE.

-- 
   What|Removed |Added

   Keywords||error-recovery, ice-on-
   ||invalid-code


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23155


[Bug libstdc++/22205] [4.1 Regression] errors debug mode on aix

2005-07-30 Thread dje at gcc dot gnu dot org

--- Additional Comments From dje at gcc dot gnu dot org  2005-07-31 04:25 
---
I tried overriding libstdc++'s definition of __GXX_WEAK__ and GCC's definition
of ONE_ONLY.  Both caused additional C++ testsuite failures.  AIX does support
weak, but not exactly the way that G++ is expecting.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22205


[Bug testsuite/23149] gcov test assertion naming

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
04:42 ---
Confirmed.

-- 
   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed||1
   Last reconfirmed|-00-00 00:00:00 |2005-07-31 04:42:31
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23149


[Bug c++/19776] compiler crash (segmentation fault)

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
04:58 ---
This is a dup of bug 22139.  The reason for the errors in 4.0.1 and above:
class a
{
  friend class b;
  b f(void);
};

is invalid code.

*** This bug has been marked as a duplicate of 22139 ***

-- 
   What|Removed |Added

 Status|WAITING |RESOLVED
   Keywords||ice-on-valid-code
 Resolution||DUPLICATE
   Target Milestone|--- |4.0.2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19776


[Bug c++/22139] [4.0/4.1 regression] Segfault with templates and friend functions

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
04:58 ---
*** Bug 19776 has been marked as a duplicate of this bug. ***

-- 
   What|Removed |Added

 CC||peter at syncad dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22139


[Bug rtl-optimization/15414] Failure in compiling very huge C program

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
05:17 ---
Hmm, on powerpc-darwin on the mainline, we spike up to 900MB for some reason 
and then drop back 
down to 400MB.

-- 
   What|Removed |Added

 Status|WAITING |NEW
 GCC target triplet||powerpc-darwin
   Last reconfirmed|2005-06-25 13:16:51 |2005-07-31 05:17:07
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15414


[Bug rtl-optimization/15414] Failure in compiling very huge C program

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
05:36 ---
The memory is not in GC at all.  I don't which pass is allocating the memory.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15414


[Bug c++/23156] New: Fails valid? (valid according to Comeau anyway)

2005-07-30 Thread igodard at pacbell dot net
typedef int A;
struct foo{
A A;
};

compiles in 3.4.0 and on Comeau, but on 3.4.2 you get:


changedMeaning.cc:3: error: declaration of `A foo::A'
changedMeaning.cc:1: error: changes meaning of `A' from `typedef int A'

So who's right, you or EDG?

Ivan

-- 
   Summary: Fails valid? (valid according to Comeau anyway)
   Product: gcc
   Version: 3.4.2
Status: UNCONFIRMED
  Severity: normal
  Priority: P2
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: igodard at pacbell dot net
CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23156


[Bug c++/23156] Fails valid? (valid according to Comeau anyway)

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
05:39 ---
GCC is.  See PR 17353 and [basic.scope.class] of the standard.

*** This bug has been marked as a duplicate of 17353 ***

-- 
   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23156


[Bug c++/17353] type name in nested class conflicts with name in outer class

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
05:39 ---
*** Bug 23156 has been marked as a duplicate of this bug. ***

-- 
   What|Removed |Added

 CC||igodard at pacbell dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17353


[Bug c++/17644] unexpected symbol redefinition error

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
05:40 ---
Reopening to ...

-- 
   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17644


[Bug c++/17644] unexpected symbol redefinition error

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
05:40 ---
Mark as a dup of bug 17353.

*** This bug has been marked as a duplicate of 17353 ***

-- 
   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17644


[Bug c++/17353] type name in nested class conflicts with name in outer class

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
05:40 ---
*** Bug 17644 has been marked as a duplicate of this bug. ***

-- 
   What|Removed |Added

 CC||boris at kolpackov dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17353


[Bug c++/17605] Using types as names in classes not always allowed

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
05:41 ---
Reopening to ...

-- 
   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17605


[Bug c++/17605] Using types as names in classes not always allowed

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
05:41 ---
As a dup of bug 17353.

*** This bug has been marked as a duplicate of 17353 ***

-- 
   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17605


[Bug c++/17353] type name in nested class conflicts with name in outer class

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
05:41 ---
*** Bug 17605 has been marked as a duplicate of this bug. ***

-- 
   What|Removed |Added

 CC||djn at daimi dot au dot dk


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17353


[Bug c++/18320] version drift 3.4.0->3.4.2?

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
05:42 ---
Reopening to ...

-- 
   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|DUPLICATE   |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18320


[Bug c++/18320] version drift 3.4.0->3.4.2?

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
05:42 ---
Mark as a dup of bug 17353.

*** This bug has been marked as a duplicate of 17353 ***

-- 
   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18320


[Bug c++/17353] type name in nested class conflicts with name in outer class

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
05:42 ---
*** Bug 18320 has been marked as a duplicate of this bug. ***

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17353


[Bug tree-optimization/21559] [4.1 Regression] missed jump threading

2005-07-30 Thread phython at gcc dot gnu dot org

--- Additional Comments From phython at gcc dot gnu dot org  2005-07-31 
05:45 ---
 I would really prefer option b, where we keep VRP information persistant.  That
way fold can use VRP information when available.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21559


[Bug libfortran/23154] Bad floating point in formatted read

2005-07-30 Thread jvdelisle at gcc dot gnu dot org

--- Additional Comments From jvdelisle at gcc dot gnu dot org  2005-07-31 
05:52 ---
I have instrumented a few places in transfer.c.  In particular looking at the
string at 'q' in sf_read.  The original string is corrupted before getting to
the first read.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23154


[Bug gcov/profile/12786] -fvpt does not work with signed mod or signed divide with a constant negative number

2005-07-30 Thread pinskia at gcc dot gnu dot org

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 
06:07 ---
Fixed on the mainline by moving over to the tree based profiling.

-- 
   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED
   Target Milestone|--- |4.1.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12786


[Bug libfortran/23154] Bad floating point in formatted read

2005-07-30 Thread jvdelisle at gcc dot gnu dot org

--- Additional Comments From jvdelisle at gcc dot gnu dot org  2005-07-31 
06:15 ---
Created an attachment (id=9389)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9389&action=view)
Revised test case to honor 72 column magic

The revised test case here, remembering not to exceed 72 columns with the
important text no longer shows the problem.  So this testcase does not reflect
the situation in the original problem.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23154


[Bug libfortran/23154] Bad floating point in formatted read

2005-07-30 Thread jvdelisle at gcc dot gnu dot org

--- Additional Comments From jvdelisle at gcc dot gnu dot org  2005-07-31 
06:47 ---
Reference information on this thread:

http://gcc.gnu.org/ml/fortran/2005-07/msg00495.html



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23154