Hi Maciej,
Thanks for the update. I've read through the whole proposal again and
it looks good. I'd like to discuss legacy objects a bit more though...
Maciej Rozycki writes:
> 3.4 Relocatable Object Generation
>
> Tools that produce relocatable objects such as the assembler shall
> always p
On 05/08/2016 03:27 PM, David Wohlferd wrote:
Looking at the v6 release criteria (https://gcc.gnu.org/gcc-6/criteria.html)
there are about a dozen
supported platforms.
Looking at the Machine Constraints docs
(https://gcc.gnu.org/onlinedocs/gcc/Machine-Constraints.html), there are 34
architectu
Hello,
My name is Jessica Lowe, I am a middle school teacher in Colorado. I have been
working with a student of mine who is interested in learning more about
computer coding and programming. I was doing some research and finding some
sources for him, and I found your page https://gcc.gnu.org/re
Hi,
Here's a report of a successful build and install of GCC:
$ gcc-6.1.0/config.guess
armv5tel-unknown-linux-gnueabi
$ newcompiler/bin/gcc -v
Using built-in specs.
COLLECT_GCC=newcompiler/bin/gcc
COLLECT_LTO_WRAPPER=/mnt/gcctest/newcompiler/libexec/gcc/arm-unknown-linux-gnueabi/6.1.0/lto-wrappe
On 05/15/2016 03:43 AM, Woon yung Liu wrote:
testv.c:70:2: note: ==> examining statement: _5 = (int) _4;
You need to implement the vec_unpack* patterns.
But how can I tell what operations are required by autovectorization, that are
currently not supported?
Well, the dumps you're looking
On 05/14/2016 03:21 AM, Woon yung Liu wrote:
The current constraints allow GCC to access the 64-bit LO+HI register pair
as a single 128-bit register, so I am cheating by using both the x and wr
(new constraint for LO1+HI1) constraints.
That doesn't seem right.
The x constrant is for the hi/lo
Hi All ,
We are migrating to the gold linker and see the below issue
bash-4.1$ /auto/compiler-migration/bin/armeb-linux-gnueabi-ld.gold --be8
/auto/compiler-migration/bin/armeb-linux-gnueabi-ld.gold: --be8: unknown option
Any help ,will be appreciated .
Thank you
~Umesh
