Hello,
I would like to update the documentation of these compiler flags and
have some questions. The -ffunction-sections and -fdata-sections
documentation is currently:
"Place each function or data item into its own section in the output
file if the target supports arbitrary sections. The n
On Fri, Oct 13, 2017 at 3:06 AM, Sebastian Huber
wrote:
> Hello,
>
> I would like to update the documentation of these compiler flags and have
> some questions. The -ffunction-sections and -fdata-sections documentation
> is currently:
>
> "Place each function or data item into its own section in
On 10/13/2017 01:06 AM, Sebastian Huber wrote:
> Hello,
>
> I would like to update the documentation of these compiler flags and
> have some questions. The -ffunction-sections and -fdata-sections
> documentation is currently:
>
> "Place each function or data item into its own section in the outp
On 10/12/2017 10:49 PM, Oren Ben-Kiki wrote:
On Fri, Oct 13, 2017 at 4:47 AM, Martin Sebor mailto:mse...@gmail.com>> wrote:
My organization was particularly focused on warnings so I'm quite
familiar with the challenges you're hoping to overcome.
I figured I wasn't the only one :-) Bu
On 13 October 2017 at 17:02, David Edelsohn wrote:
> On Fri, Oct 13, 2017 at 3:06 AM, Sebastian Huber
> wrote:
>> Hello,
>>
>> I would like to update the documentation of these compiler flags and have
>> some questions. The -ffunction-sections and -fdata-sections documentation
>> is currently:
>
My team and I are working on a procedural abstraction (PA)
optimization for GCC based on the ARM Embedded Toolchain
distribution that uses GCC 6.2.1. Our initial attempt to get
something functional has been successful, but it is a very messy
solution because we don't see a reasonable way to do
- Am 13. Okt 2017 um 16:02 schrieb David Edelsohn dje@gmail.com:
> On Fri, Oct 13, 2017 at 3:06 AM, Sebastian Huber
> wrote:
>> Hello,
>>
>> I would like to update the documentation of these compiler flags and have
>> some questions. The -ffunction-sections and -fdata-sections documentat
On 10/13/2017 12:18 PM, Geoff Wozniak wrote:
> My team and I are working on a procedural abstraction (PA) optimization
> for GCC based on the ARM Embedded Toolchain distribution that uses GCC
> 6.2.1. Our initial attempt to get something functional has been
> successful, but it is a very messy solu
- Am 13. Okt 2017 um 16:11 schrieb Jeff Law l...@redhat.com:
> On 10/13/2017 01:06 AM, Sebastian Huber wrote:
>> Hello,
>>
>> I would like to update the documentation of these compiler flags and
>> have some questions. The -ffunction-sections and -fdata-sections
>> documentation is currently
On Fri, Oct 13, 2017 at 2:34 PM, Sebastian Huber
wrote:
>>> Do these options affect the code generation?
>> They can affect code generation. By placing each object into its own
>> section it's no longer viable to use one object to refer to another
>> because the relative addresses are unknown u
- Am 13. Okt 2017 um 20:39 schrieb David Edelsohn dje@gmail.com:
> On Fri, Oct 13, 2017 at 2:34 PM, Sebastian Huber
> wrote:
>
Do these options affect the code generation?
>>> They can affect code generation. By placing each object into its own
>>> section it's no longer viable
>> It places each function and each datum into a separate section, which
>> can be placed or removed independently. It is not combining data or
>> altering the order of structures. It allows the linker to position
>> functions and data items as individual components instead of a single
>> object
On 10/13/2017 12:45 PM, Sebastian Huber wrote:
>
>
> - Am 13. Okt 2017 um 20:39 schrieb David Edelsohn dje@gmail.com:
>
>> On Fri, Oct 13, 2017 at 2:34 PM, Sebastian Huber
>> wrote:
>>
> Do these options affect the code generation?
They can affect code generation. By placing
On Thu, Oct 12, 2017 at 4:46 AM, Oren Ben-Kiki wrote:
> Motivation/Use case:
>
> * Since gcc/g++ intentionally does not have `-Weverything`, there is a
> number of explicit `-W...` flags one might wish to specify explicitly. Fair
> enough.
>
> * Additional `-W...` flags are introduced in new gcc/g
On 10/13/2017 12:06 AM, Sebastian Huber wrote:
The end-of-life of Solaris 2.6 was 2006. Is it worth to mention this here?
The reference to Solaris 2.6 is no longer useful. Just mention ELF here.
This "AIX may have these optimizations in the future." is there since at
least 1996. What is the
On Wed, 2017-10-11 at 16:17 +0200, Marc Glisse wrote:
> On Wed, 11 Oct 2017, David Malcolm wrote:
>
> > On Wed, 2017-10-11 at 11:18 +0200, Paulo Matos wrote:
> > >
> > > On 11/10/17 11:15, Christophe Lyon wrote:
> > > >
> > > > You can have a look at
> > > > https://git.linaro.org/toolchain/gcc-
16 matches
Mail list logo