This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/19699] [4.0/4.1 Regression] warning about not returning from end of a non-void function because of dead code
- From: "veksler at il dot ibm dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Jun 2005 15:20:10 -0000
- Subject: [Bug middle-end/19699] [4.0/4.1 Regression] warning about not returning from end of a non-void function because of dead code
- References: <20050129192214.19699.pinskia@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From veksler at il dot ibm dot com 2005-06-06 15:20 -------
(In reply to comment #13)
> (In reply to comment #12)
> > Will the patch be applied to 4.0 branch too?
> No because it is too big in that it also changes the inliner to be a CFG aware
inliner.
In that case, it should not be marked "RESOLVED" for gcc-4.0 until:
1. either it is marked WONTFIX for gcc-4.0
2. or a new patch is written specifically for the gcc-4.0 branch.
>From comment #2 I understand that option 2 is out of the question.
Does it mean that "gcc-4.0 is dead, long live gcc-4.1" ?
This is how I came to this "conclusion":
There are new (not very rare) regressions in gcc-4.0 that will never
be fixed. These regressions will be fixed only in gcc-4.1.
As a result, it sounds like gcc-4.0 is much less maintained than
any other (active) branch (or trunk) at the moment. This is
very different from any of the previous releases of GCC (up to
gcc-2.95)
If this is true, then gcc-4.1 schedule should be changed
to reflect that.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19699