--- Comment #6 from martin at mpa-garching dot mpg dot de 2007-04-27 08:02
---
I confirm that this is fixed for me on mainline.
Is the patch non-invasive enough for a backport to 4.2 (possibly after the
4.2.0 release)?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25923
--- Comment #5 from simartin at gcc dot gnu dot org 2007-04-24 21:52
---
Subject: Bug 25923
Author: simartin
Date: Tue Apr 24 21:52:16 2007
New Revision: 124121
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=124121
Log:
2007-04-24 Simon Martin [EMAIL PROTECTED]
PR
--- Comment #4 from patchapp at dberlin dot org 2007-04-22 10:35 ---
Subject: Bug number PR diagnostic/25923
A patch for this bug has been added to the patch tracker.
The mailing list url for the patch is
http://gcc.gnu.org/ml/gcc-patches/2007-04/msg01388.html
--
--- Comment #3 from aldot at gcc dot gnu dot org 2006-10-13 11:54 ---
To me this sounds more like a middle-end issue. The ME apparently doesn't have
means to use language specific diagnosics hooks.
Also see comment #2 for PR24784 at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24784#c2
--- Comment #2 from martin at mpa-garching dot mpg dot de 2006-06-06 10:14
---
Is it possible to fix this before gcc 4.2?
Whenever I see these garbled warnings I have a very bad feeling that
something completely unintended is happening inside the compiler,
and I guess that many users
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-01-23 16:18 ---
Confirmed.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
