This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Question about ASMCONS
- From: Claudiu Zissulescu <claziss at gmail dot com>
- To: Segher Boessenkool <segher at kernel dot crashing dot org>
- Cc: Claudiu Zissulescu <Claudiu dot Zissulescu at synopsys dot com>, gcc at gcc dot gnu dot org, Francois Bedard <Francois dot Bedard at synopsys dot com>, bergner at linux dot ibm dot com
- Date: Tue, 11 Dec 2018 13:28:31 +0200
- Subject: Re: Question about ASMCONS
- References: <098ECE41A0A6114BB2A07F1EC238DE89661BEC1A@de02wembxa.internal.synopsys.com> <20161219170621.GA11295@gate.crashing.org> <2a91debf-953d-f0a5-0dad-72024c628f00@gmail.com> <CAL0iMy19sqybCWcXoxep7T+_ucd9-1B=61D=3gMi_EU8KoHPFg@mail.gmail.com> <20181211103350.GL3803@gate.crashing.org>
Hi,
Thank you for the quick response, but I still get it with the latest
gcc sources. The error is shown only when the compiler is configured
with all the internal checks in place. Please, can you share with me
the way how you build the toolchain. I am trying to see what I do
wrong...
Thank you,
Claudiu
On Tue, Dec 11, 2018 at 12:34 PM Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> Hi!
>
> On Tue, Dec 11, 2018 at 12:02:42PM +0200, Claudiu Zissulescu wrote:
> > This issue still keeps biting me, specially in the glibc upstreaming
> > process. I have made a bugzilla entry for this
> > (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88001) where I also
> > added my solution for the given issue.
> >
> > Please can someone help me, or maybe let me know if my patch is acceptable?
>
> I have good news for you. The problem reproduced with my 20181025
> compiler, but between then and now the problem was fixed -- probably
> one of Peter's IRA patches, which dealt with exactly this kind of
> problem :-)
>
>
> Segher