This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH, M2] Compiler driver patches
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Gaius Mulley <gaius dot mulley at southwales dot ac dot uk>
- Cc: <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 20 Nov 2013 22:47:52 +0000
- Subject: Re: [PATCH, M2] Compiler driver patches
- Authentication-results: sourceware.org; auth=none
- References: <87hab7vt8i dot fsf at j228-gm dot comp dot glam dot ac dot uk> <Pine dot LNX dot 4 dot 64 dot 1311201825290 dot 28804 at digraph dot polyomino dot org dot uk> <87siuq690i dot fsf at j228-gm dot comp dot glam dot ac dot uk>
On Wed, 20 Nov 2013, Gaius Mulley wrote:
> Thanks for all the comments regarding the set of patches. Perhaps the
> statement "use its own linker" is misleading. When gm2 is asked to link
> a module hello.mod it does the following:
Thanks for the explanation. I think this is sufficiently complicated that
driver patches to facilitate it can't effectively be reviewed separately
from the gm2 driver itself (i.e. the two patches should be posted for
review at the same time), unless the driver patches make sense as cleanups
in their own right in the context of the front ends already in tree.
The sort of change that's more suitable for review indepedent of the front
end would be e.g. fixes for optimization bugs where you've only triggered
the bug with M2 input but will propose the patch on the basis that the
GIMPLE produced by the front end is valid and is being transformed in an
invalid way, even if no other front end produces that GIMPLE.
--
Joseph S. Myers
joseph@codesourcery.com