The trunk is in Stage 3 now, which means it is open for general
bugfixing.
Patches posted early enough during Stage 1 and not yet fully reviewed
may still get in early in Stage 3. Please make sure to ping them
soon enough.
Still misleading quality data below - P3 bugs have not been
re-prioritiz
On Fri, Nov 14, 2014 at 4:27 PM, David Malcolm wrote:
> On Thu, 2014-11-13 at 11:45 +0100, Richard Biener wrote:
>> On Thu, Nov 13, 2014 at 2:41 AM, David Malcolm wrote:
>> > On Tue, 2014-11-11 at 11:43 +0100, Richard Biener wrote:
>> >> On Tue, Nov 11, 2014 at 8:26 AM, Jakub Jelinek wrote:
>> >
On Sat, Nov 15, 2014 at 12:00 PM, David Malcolm wrote:
> On Thu, 2014-11-13 at 11:45 +0100, Richard Biener wrote:
>> On Thu, Nov 13, 2014 at 2:41 AM, David Malcolm wrote:
>> > On Tue, 2014-11-11 at 11:43 +0100, Richard Biener wrote:
>> >> On Tue, Nov 11, 2014 at 8:26 AM, Jakub Jelinek wrote:
>>
On Sun, Nov 16, 2014 at 10:08 PM, David Edelsohn wrote:
> Because they have not shown general performance benefit.
Also they very often cause very long compile-times.
> I hope that the renewed attention and development effort will allow
> them to be enabled by default eventually.
Yeah - though
Hello All:
I was looking at the optimized usage and allocation to argument registers.
There are two aspects to it as follows.
1. We need to specify the argument registers as followed by ABI in the target
specific code. Based on the function
argument registers defined in the target dependent co
Hi,
On Thu, 13 Nov 2014, H.J. Lu wrote:
> @GOTPLT will create a PLT entry, but it doesn't mean PLT entry will be
> used.
Correct. The compiler was supposed to somehow make a good decision (e.g.
if there were calls and address-takings in the same unit).
> Only @PLTOFF will use PLT entry. Lin
Hi,
On Thu, 13 Nov 2014, H.J. Lu wrote:
> Linker does:
>
> ... code that looks like it might create just one GOT slot ...
>
> So if a symbol is accessed by both @GOT and @PLTOFF, its
> needs_plt will be true and its got.plt entry will be used for
> both @GOT and @GOTPLT. @GOTPLT has no advant
On 11/17/14 06:13, Ajit Kumar Agarwal wrote:
Hello All:
I was looking at the optimized usage and allocation to argument registers.
There are two aspects to it as follows.
1. We need to specify the argument registers as followed by ABI in the target
specific code. Based on the function
argum
On 11/14/14 08:27, David Malcolm wrote:
I just don't like all the as_a/is_a stuff enforced everywhere,
it means more typing, more temporaries, more indentation.
So, as I view it, instead of the checks being done cheaply (yes, I think
the gimple checking as we have right now is very cheap) under
On 11/17/14 03:06, Richard Biener wrote:
Also, presumably if this were merged, it would require a followup with
the gimple to gimple * fixup you wanted? (which we talked about doing as
an early stage3 thing IIRC [1]).
Yeah, that would be nice (to remind people - this is about getting rid
of
On 2014-11-17 8:13 AM, Ajit Kumar Agarwal wrote:
Hello All:
I was looking at the optimized usage and allocation to argument registers.
There are two aspects to it as follows.
1. We need to specify the argument registers as followed by ABI in the target
specific code. Based on the function
a
On Mon, Nov 17, 2014 at 6:14 AM, Michael Matz wrote:
> Hi,
>
> On Thu, 13 Nov 2014, H.J. Lu wrote:
>
>> Linker does:
>>
>> ... code that looks like it might create just one GOT slot ...
>>
>> So if a symbol is accessed by both @GOT and @PLTOFF, its
>> needs_plt will be true and its got.plt entry
On Mon, 2014-11-17 at 11:06 +0100, Richard Biener wrote:
> On Sat, Nov 15, 2014 at 12:00 PM, David Malcolm wrote:
> > On Thu, 2014-11-13 at 11:45 +0100, Richard Biener wrote:
> >> On Thu, Nov 13, 2014 at 2:41 AM, David Malcolm wrote:
> >> > On Tue, 2014-11-11 at 11:43 +0100, Richard Biener wrote:
13 matches
Mail list logo
