This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/24222] The gimplifier shouldn't emit warnings or errors
- From: "sabre at nondot dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Oct 2005 01:51:58 -0000
- Subject: [Bug c++/24222] The gimplifier shouldn't emit warnings or errors
- References: <bug-24222-6809@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from sabre at nondot dot org 2005-10-06 01:51 -------
The gimplifier apparently emits these three errors:
error ("memory input %d is not directly addressable", i);
error ("invalid lvalue in asm output %d", i);
error ("too few arguments to function %<va_start%>");
In an ideal, modular, world, the front-ends should be emitting these. If these
checks need to be shared across different front-ends, the checks could be
function calls in c-common, not be put into the gimplifier.
One immediate advantage would be that -fsyntax-only wouldn't need to run the
gimplifier.
-Chris
--
sabre at nondot dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|-fsyntax-only runs the |The gimplifier shouldn't
|gimplifier |emit warnings or errors
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24222