On Wed, 24 Aug 2016, Claudiu Zissulescu wrote:
1) Does the patch break things for people using an older compiler? (how
old?) Is it worth having both versions with an #if on the compiler
version?
No, J is really old, very probably there is no compiler around (besides
the ones in archives) that
Hi,
>
> 1) Does the patch break things for people using an older compiler? (how
> old?) Is it worth having both versions with an #if on the compiler
> version?
No, J is really old, very probably there is no compiler around (besides the
ones in archives) that supports this constraint letter as t
On Wed, 24 Aug 2016, Claudiu Zissulescu wrote:
The J-constant was mainly used by Arc 4 architecture for 32-bit integer
constants. It got obsoleted once we pushed the new ARCompact
architecture to gcc (GCC5.x+). The replace constraint is the Cal which
is again a 32 bit constraint fitted for ari
Hello,
I got inspiration from the following gcc patch:
https://gcc.gnu.org/ml/gcc-patches/2016-04/msg01964.html
"J" constraint is rejected with recent gcc, so we have to replace it.
Adding to "CC" our GCC maintainer, he can give better comments if you have any
further questions.
On Mon, 2016-
Hello,
The J-constant was mainly used by Arc 4 architecture for 32-bit integer
constants. It got obsoleted once we pushed the new ARCompact architecture to
gcc (GCC5.x+). The replace constraint is the Cal which is again a 32 bit
constraint fitted for arithmetic ops.
Thank you,
Claudiu
> -
