On Tue, Jun 25, 2019 at 10:14 AM Martin Liška wrote:
>
> On 6/24/19 8:05 PM, Richard Biener wrote:
> > On Mon, Jun 24, 2019 at 3:31 PM Martin Liška wrote:
> >>
> >> On 6/24/19 2:44 PM, Richard Biener wrote:
> >>> On Mon, Jun 24, 2019 at 2:12 PM Martin Liška wrote:
>
> On 6/24/19 2:02 P
On 6/24/19 8:05 PM, Richard Biener wrote:
> On Mon, Jun 24, 2019 at 3:31 PM Martin Liška wrote:
>>
>> On 6/24/19 2:44 PM, Richard Biener wrote:
>>> On Mon, Jun 24, 2019 at 2:12 PM Martin Liška wrote:
On 6/24/19 2:02 PM, Richard Biener wrote:
> On Fri, Jun 21, 2019 at 4:01 PM Martin
On Mon, Jun 24, 2019 at 3:31 PM Martin Liška wrote:
>
> On 6/24/19 2:44 PM, Richard Biener wrote:
> > On Mon, Jun 24, 2019 at 2:12 PM Martin Liška wrote:
> >>
> >> On 6/24/19 2:02 PM, Richard Biener wrote:
> >>> On Fri, Jun 21, 2019 at 4:01 PM Martin Liška wrote:
>
> On 6/21/19 2:57 PM
> On 24 Jun 2019, at 14:31, Martin Liška wrote:
>
> On 6/24/19 2:44 PM, Richard Biener wrote:
>> On Mon, Jun 24, 2019 at 2:12 PM Martin Liška wrote:
>>>
>>> On 6/24/19 2:02 PM, Richard Biener wrote:
On Fri, Jun 21, 2019 at 4:01 PM Martin Liška wrote:
>
> On 6/21/19 2:57 PM, Jan
On 6/24/19 2:44 PM, Richard Biener wrote:
> On Mon, Jun 24, 2019 at 2:12 PM Martin Liška wrote:
>>
>> On 6/24/19 2:02 PM, Richard Biener wrote:
>>> On Fri, Jun 21, 2019 at 4:01 PM Martin Liška wrote:
On 6/21/19 2:57 PM, Jan Hubicka wrote:
> This looks like good step (and please stre
On Mon, Jun 24, 2019 at 2:12 PM Martin Liška wrote:
>
> On 6/24/19 2:02 PM, Richard Biener wrote:
> > On Fri, Jun 21, 2019 at 4:01 PM Martin Liška wrote:
> >>
> >> On 6/21/19 2:57 PM, Jan Hubicka wrote:
> >>> This looks like good step (and please stream it in host independent
> >>> way). I suppos
On 6/24/19 2:02 PM, Richard Biener wrote:
> On Fri, Jun 21, 2019 at 4:01 PM Martin Liška wrote:
>>
>> On 6/21/19 2:57 PM, Jan Hubicka wrote:
>>> This looks like good step (and please stream it in host independent
>>> way). I suppose all these issues can be done one-by-one.
>>
>> So there's a worki
On Fri, Jun 21, 2019 at 4:01 PM Martin Liška wrote:
>
> On 6/21/19 2:57 PM, Jan Hubicka wrote:
> > This looks like good step (and please stream it in host independent
> > way). I suppose all these issues can be done one-by-one.
>
> So there's a working patch for that. However one will see followin
On 6/21/19 2:57 PM, Jan Hubicka wrote:
> This looks like good step (and please stream it in host independent
> way). I suppose all these issues can be done one-by-one.
So there's a working patch for that. However one will see following errors
when using an older compiler or older LTO bytecode:
$
> On 6/21/19 2:34 PM, Richard Biener wrote:
> > On Fri, Jun 21, 2019 at 12:20 PM Martin Liška wrote:
> >>
> >> Hi.
> >>
> >> The patch is about a new ELF section that will contain information
> >> about LTO version. And for the future, used compression will be stored
> >> here. The patch removes s
On 6/21/19 2:34 PM, Richard Biener wrote:
> On Fri, Jun 21, 2019 at 12:20 PM Martin Liška wrote:
>>
>> Hi.
>>
>> The patch is about a new ELF section that will contain information
>> about LTO version. And for the future, used compression will be stored
>> here. The patch removes streaming of the
On Fri, Jun 21, 2019 at 12:20 PM Martin Liška wrote:
>
> Hi.
>
> The patch is about a new ELF section that will contain information
> about LTO version. And for the future, used compression will be stored
> here. The patch removes streaming of the version into each section.
I'd like each section
patch.
Thoughts?
Martin
>From a694d3244812bb8c0ae79d3ef5aecc6f5a2bd9ca Mon Sep 17 00:00:00 2001
From: Martin Liska
Date: Fri, 21 Jun 2019 12:14:04 +0200
Subject: [PATCH] Add .gnu.lto_.meta section.
gcc/ChangeLog:
2019-06-21 Martin Liska
* lto-section-in.c (lto_get_section_data): Do not
de
13 matches
Mail list logo