This is the mail archive of the gcc-patches@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: [patch] Do not call output_constant from the front end

From: Steven Bosscher <stevenb dot gcc at gmail dot com>
To: Eric Botcazou <ebotcazou at adacore dot com>
Cc: gcc-patches at gcc dot gnu dot org, java-patches at gcc dot gnu dot org, Richard Guenther <richard dot guenther at gmail dot com>
Date: Tue, 27 Mar 2012 23:51:46 +0200
Subject: Re: [patch] Do not call output_constant from the front end
References: <CABu31nPAkz+xn4OVa-N+zee0b44TYd-rqQgSVg=m7+NxOMyTqg@mail.gmail.com> <201203272307.17027.ebotcazou@adacore.com>

On Tue, Mar 27, 2012 at 11:07 PM, Eric Botcazou <ebotcazou@adacore.com> wrote:
>> With this patch a variable named "_Jv_CLS" is written out. The
>> assembly before and after the patch is the same, except for the
>> variable name. I want to write out a nameless variable but I don't
>> know how.
>
> Try tree_output_constant_def.

I didn't know about this function. But as far as I can tell, there is
no way to instruct that function to put the data in a specific
section. In the Java case, the data must be put in the .jcr section. I
suppose that can be achieved with a bit more re-working of varasm, but
not with the code as-is. Thanks for the pointer, though!

Ciao!
Steven

Follow-Ups:
- [patch][rfa] Do not call output_constant from the front end
  - From: Steven Bosscher

References:
- [patch] Do not call output_constant from the front end
  - From: Steven Bosscher
- Re: [patch] Do not call output_constant from the front end
  - From: Eric Botcazou

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