On Thu, 18 Jul 2019, Florian Weimer wrote:
> > Right and stable LTO bytecode really isn't on the radar at this time.
>
> Maybe it's better to serialize the non-preprocessed source code instead.
> It would need some (hash-based?) deduplication. For #include
> directives, the hash of the file would
Snapshot gcc-7-20190718 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20190718/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7
* Jeff Law:
> On 7/17/19 11:29 AM, Andi Kleen wrote:
>> Romain Geissler writes:
>>>
>>> I have no idea of the LTO format and if indeed it can easily be updated
>>> in a backward compatible way. But I would say it would be nice if it
>>> could, and would allow adoption for projects spread on many
On Wed, Jul 17, 2019 at 7:30 PM Andi Kleen wrote:
>
> Romain Geissler writes:
> >
> > I have no idea of the LTO format and if indeed it can easily be updated
> > in a backward compatible way. But I would say it would be nice if it
> > could, and would allow adoption for projects spread on many te
Hi!
If you're doing cool things in the area of "Accelerator Programming using
Directives" or related things, please consider submitting a paper. (I'm
on the Program Committee again.)
|
| Sixth Workshop on Accelerator Progra
