Hello,
I would like to configure a bi-arch PowerPC GCC. My naive approach was
simply:
diff --git a/gcc/config.gcc b/gcc/config.gcc
index 90308cd..228f941 100644
--- a/gcc/config.gcc
+++ b/gcc/config.gcc
@@ -2381,7 +2381,7 @@ powerpc-*-eabi*)
use_gcc_stdint=wrap
;;
powerpc-*-rt
Hi,
On Thu, Jan 19, 2017 at 01:41:33PM +0100, Sebastian Huber wrote:
> conftest.c:16:1: error: unrecognizable insn:
> }
> ^
> (insn/f 22 21 23 2 (parallel [
> (set (reg/f:DI 1 1)
> (plus:SI (reg/f:DI 1 1)
> (const_int 16 [0x10])))
> (se
Hello Segher,
On 20/01/17 02:04, Segher Boessenkool wrote:
Hi,
On Thu, Jan 19, 2017 at 01:41:33PM +0100, Sebastian Huber wrote:
conftest.c:16:1: error: unrecognizable insn:
}
^
(insn/f 22 21 23 2 (parallel [
(set (reg/f:DI 1 1)
(plus:SI (reg/f:DI 1 1)
On Fri, Jan 20, 2017 at 08:35:14AM +0100, Sebastian Huber wrote:
> >so you seem to have 64-bit ABI_V4? I wonder how well tested that is,
> >you are likely to run into more problems. Either stack_restore_tie or
> >the above code will need a tweak.
>
> thanks for your help. I would had a hard time
On 21/01/17 01:46, Segher Boessenkool wrote:
On Fri, Jan 20, 2017 at 08:35:14AM +0100, Sebastian Huber wrote:
so you seem to have 64-bit ABI_V4? I wonder how well tested that is,
you are likely to run into more problems. Either stack_restore_tie or
the above code will need a tweak.
thanks for
Hello again,
On Mon, Jan 23, 2017 at 09:19:04AM +0100, Sebastian Huber wrote:
> >>I am flexible in terms of the ABI choice for the 64-bit PowerPC. I guess
> >>the ABI_ELFv2 is the way to go?
> >It certainly is the most modern ABI. It makes some requirements to what
> >Power ISA features are requi
On 23/01/17 18:18, Segher Boessenkool wrote:
Hello again,
On Mon, Jan 23, 2017 at 09:19:04AM +0100, Sebastian Huber wrote:
I am flexible in terms of the ABI choice for the 64-bit PowerPC. I guess
the ABI_ELFv2 is the way to go?
It certainly is the most modern ABI. It makes some requirements t
On Wed, Jan 25, 2017 at 01:11:49PM +0100, Sebastian Huber wrote:
> I still get a lot of ICEs with the attached two patches (examples):
> /home/EB/sebastian_h/archive/gcc-git/libgcc/libgcc2.c: In function
> '__multc3':
> /home/EB/sebastian_h/archive/gcc-git/libgcc/libgcc2.c:2035:1: error:
> unrec
On 25/01/17 18:55, Segher Boessenkool wrote:
On Wed, Jan 25, 2017 at 01:11:49PM +0100, Sebastian Huber wrote:
>I still get a lot of ICEs with the attached two patches (examples):
>/home/EB/sebastian_h/archive/gcc-git/libgcc/libgcc2.c: In function
>'__multc3':
>/home/EB/sebastian_h/archive/gcc-gi
On 30/01/17 11:38, Sebastian Huber wrote:
On 25/01/17 18:55, Segher Boessenkool wrote:
On Wed, Jan 25, 2017 at 01:11:49PM +0100, Sebastian Huber wrote:
>I still get a lot of ICEs with the attached two patches (examples):
>/home/EB/sebastian_h/archive/gcc-git/libgcc/libgcc2.c: In function
>'__
Hi,
On Mon, Jan 30, 2017 at 01:13:13PM +0100, Sebastian Huber wrote:
> The compiler build shows these warnings:
>
> /home/EB/sebastian_h/archive/gcc-git/gcc/config/rs6000/rs6000.md:11023:1:
> warning: source missing a mode?
> /home/EB/sebastian_h/archive/gcc-git/gcc/config/rs6000/rs6000.md:11034
On Mon, Jan 30, 2017 at 11:38:19AM +0100, Sebastian Huber wrote:
> >The IEEE128 code almost certainly has some bugs on non-Linux
> >configurations.
> >You could try debugging it, or you could avoid it (for now) by e.g. making
> >long double the same as double.
>
> If I set rs6000_long_double_type
On 30/01/17 11:38, Sebastian Huber wrote:
On 25/01/17 18:55, Segher Boessenkool wrote:
On Wed, Jan 25, 2017 at 01:11:49PM +0100, Sebastian Huber wrote:
>I still get a lot of ICEs with the attached two patches (examples):
>/home/EB/sebastian_h/archive/gcc-git/libgcc/libgcc2.c: In function
>'__
Hi!
On Thu, Jul 20, 2017 at 02:46:41PM +0200, Sebastian Huber wrote:
> xgcc -B/build/git-build/b-gcc-git-powerpc-rtems4.12/./gcc/ -mcpu=e6500
> -m64 -O2 -fpreprocessed -S test-v0.i -o /dev/null 2>&1
> test-v0.i: In function 'f':
> test-v0.i:8:1: error: unrecognizable insn:
> }
> ^
> (insn 12 11
On Jul 20 2017, Sebastian Huber wrote:
> Ok, so why do I get a "error: unrecognizable insn:"? How can I debug a
> message like this:
>
> (insn 12 11 13 2 (set (reg:CCFP 126)
> (compare:CCFP (reg:TF 123)
> (reg:TF 124))) "test-v0.i":5 -1
> (nil))
This is supposed to be ma
On 13/09/17 15:11, Andreas Schwab wrote:
On Jul 20 2017, Sebastian Huber wrote:
Ok, so why do I get a "error: unrecognizable insn:"? How can I debug a
message like this:
(insn 12 11 13 2 (set (reg:CCFP 126)
(compare:CCFP (reg:TF 123)
(reg:TF 124))) "test-v0.i":5 -1
16 matches
Mail list logo
