This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [gnat] reuse of ASTs already constructed

From: Geert Bosch <bosch at adacore dot com>
To: okellogg at users dot sourceforge dot net
Cc: gcc at gcc dot gnu dot org
Date: Mon, 20 Apr 2009 14:55:45 -0400
Subject: Re: [gnat] reuse of ASTs already constructed
References: <1239557374.7565.37.camel@tidbit.site> <D54EE02C-F57C-4D27-8A65-0C23BDD993D7@adacore.com> <1240253122.4554.64.camel@tidbit.site>

On Apr 20, 2009, at 14:45, Oliver Kellogg wrote:

It would be best to first contemplate what output a single
invocation of the compiler, with multiple compilation units
as arguments, should produce.


For an invocation
gnat1 a.adb b.adb c.adb
, the files a.{s,ali} b.{s,ali} c.{s,ali} are produced.


The back end is not prepared to produce multiple assembly files.
The "gcc" driver program also assumes each invocation produces a
single .s file.

So, if this is what you want to do, you'd have to address all these
underlying limitations first.

-Geert

Follow-Ups:
- Re: [gnat] reuse of ASTs already constructed
  - From: Oliver Kellogg
- Re: [gnat] reuse of ASTs already constructed
  - From: Oliver Kellogg

References:
- Re: [gnat] reuse of ASTs already constructed
  - From: Oliver Kellogg
- Re: [gnat] reuse of ASTs already constructed
  - From: Geert Bosch
- Re: [gnat] reuse of ASTs already constructed
  - From: Oliver Kellogg

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]