[AMD Public Use]
Hi Floarian,
> I'm including a proposal for the levels below. I use single letters for
> them, but I expect that the concrete implementation of this proposal will use
> names like “x86-100”, “x86-101”, like in the glibc patch referenced above.
> (But we can discuss other app
* Premachandra Mallappa:
> [AMD Public Use]
>
> Hi Floarian,
>
>> I'm including a proposal for the levels below. I use single letters for
>> them, but I expect that the concrete implementation of this proposal will
>> use
>> names like “x86-100”, “x86-101”, like in the glibc patch referenced a
Some background:
This is in the dreaded structure reorganization optimization that I'm
working on. It's running at LTRANS time with '-flto-partition=one'.
My issues in order of importance are:
1) In gimple-ssa.h, the equal method for ssa_name_hasher
has a segfault because the "var" field of "a"
I fully agree these names (100/101, A/B/C/D) are not very intuitive, I
recommend using isa tags by year (e.g. x64_2010, x64_2014) like the
python's platform tags (e.g. manylinux2010, manylinux2014).
Hello,
I am currently trying to migrate a gcc plugin that has been well developed
for x86 code to ARM platform (for arm-none-eabi-gcc).
Currently I did the following steps:
1. write a hello world program t.c
2. compile with the following commands:
➜ arm-none-eabi-gcc -v
..
