On 3 Nov 2017 16:55, "Wilco Dijkstra" wrote:
Almost all targets add an explict -fomit-frame-pointer in the target
specific
options. Rather than doing this in a target-specific way, do this in the
generic options so it works identically across all targets. In many cases
the
target no longer need
On 11/15/2017 10:38 AM, Wilco Dijkstra wrote:
Sandra Loosemore wrote:
I'd prefer that you remove the reference to configure options entirely
here. Nowadays most GCC users install a package provided by their OS
distribution, Linaro, etc, rather than trying to build GCC from scratch.
OK, I've
Sandra Loosemore wrote:
> I'd prefer that you remove the reference to configure options entirely
> here. Nowadays most GCC users install a package provided by their OS
> distribution, Linaro, etc, rather than trying to build GCC from scratch.
OK, I've removed that reference. Similarly the FRAM
Andreas Schwab wrote:
>> Joseph Myers wrote:
>>> On Fri, 3 Nov 2017, Wilco Dijkstra wrote:
>>>
>>> > Almost all targets add an explict -fomit-frame-pointer in the target
>>> > specific
>>> > options. Rather than doing this in a target-specific way, do this in the
>>>
>>> Which targets do not? Yo
On 11/08/2017 11:16 AM, Wilco Dijkstra wrote:
> Jeff Law wrote:
>
>> I'd actually prefer to deprecate the H8 and M68k. But assuming that's
>> not going to happen in the immediate future I think dropping frame
>> pointers on those targets is appropriate as long as we're generating
>> dwarf frame i
On Nov 08 2017, Wilco Dijkstra wrote:
> Joseph Myers wrote:
>> On Fri, 3 Nov 2017, Wilco Dijkstra wrote:
>>
>> > Almost all targets add an explict -fomit-frame-pointer in the target
>> > specific
>> > options. Rather than doing this in a target-specific way, do this in the
>>
>> Which targets d
Jeff Law wrote:
> I'd actually prefer to deprecate the H8 and M68k. But assuming that's
> not going to happen in the immediate future I think dropping frame
> pointers on those targets is appropriate as long as we're generating
> dwarf frame info.
Is there a way to check a target does not genera
On 11/08/2017 10:47 AM, Wilco Dijkstra wrote:
> Joseph Myers wrote:
>> On Fri, 3 Nov 2017, Wilco Dijkstra wrote:
>>
>>> Almost all targets add an explict -fomit-frame-pointer in the target
>>> specific
>>> options. Rather than doing this in a target-specific way, do this in the
>>
>> Which target
Joseph Myers wrote:
> On Fri, 3 Nov 2017, Wilco Dijkstra wrote:
>
> > Almost all targets add an explict -fomit-frame-pointer in the target
> > specific
> > options. Rather than doing this in a target-specific way, do this in the
>
> Which targets do not? You should explicitly list them and CC th
On 11/03/2017 10:54 AM, Wilco Dijkstra wrote:
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index
71b2445f70fd5b832c68c08e69e71d8ecad37a4a..1c56f4b12495fe97c604200ef245c9fa02684b0f
100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -7436,16 +7436,17 @@ machine-description ma
On Fri, 3 Nov 2017, Wilco Dijkstra wrote:
> Almost all targets add an explict -fomit-frame-pointer in the target specific
> options. Rather than doing this in a target-specific way, do this in the
Which targets do not? You should explicitly list them and CC their
maintainers and seek confirmat
11 matches
Mail list logo
