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
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
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,
> -Original Message-
> From: Vlad Zakharov
> Sent: Wednesday, August 24, 2016 11:51 AM
> To: gmp-devel@gmplib.org; Vlad Zakharov <vzak...@synopsys.com>
> Cc: Claudiu Zissulescu <claz...@synopsys.com>;
> alexey.brod...@synopsys.com
> Subject: Re: [PATCH] longlong.h:
On Wed, 17 Aug 2016, Vlad Zakharov wrote:
We replace obsolete "J" constraint with "Cal" constraint.
Hello,
could you give a little more information please? In particular, does "Cal"
work with older versions of gcc? Does "J" still work or is it rejected
with a recent gcc? Do they mean the
