This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFH] Uses of output.h in the front ends
- From: Tom Tromey <tromey at redhat dot com>
- To: Steven Bosscher <stevenb dot gcc at gmail dot com>
- Cc: GCC Mailing List <gcc at gcc dot gnu dot org>, Eric Botcazou <ebotcazou at adacore dot com>, Ian Lance Taylor <ian at airs dot com>, Jan Hubicha <jh at suse dot cz>, iains at gcc dot gnu dot org, nicola at gcc dot gnu dot org
- Date: Mon, 04 Jun 2012 07:32:40 -0600
- Subject: Re: [RFH] Uses of output.h in the front ends
- References: <CABu31nPyeAW8_5o9+acP4A6_OCKhRJxY-_rLF6CQr5tjeVUcPg@mail.gmail.com>
>>>>> "Steven" == Steven Bosscher <stevenb.gcc@gmail.com> writes:
[...]
Steven> java/class.c: switch_to_section (get_section (buf, flags, NULL));
Steven> java/class.c: switch_to_section (get_section (buf, flags, NULL));
Steven> I am not sure how to fix this. I think it could be fixed by having a
Steven> version of build_constant_desc that puts the data in a specific
Steven> section while wrapping up global variables in varasm.
In this particular case I'm not sure why switch_to_section is needed.
The code is also setting DECL_SECTION_NAME -- is that not enough?
It seems to be enough elsewhere in the same file ... see
emit_register_classes_in_jcr_section further down.
Tom