From: Zack Weinberg <zackw@panix.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
"libc-alpha @ sourceware . org" <libc-alpha@sourceware.org>,
linux-snps-arc@lists.infradead.org,
Cupertino.Miranda@synopsys.com
Subject: Re: [RFC 2/6] ARC: Fixed inline asm contraints to gcc 6.x
Date: Tue, 27 Jun 2017 16:54:00 -0000 [thread overview]
Message-ID: <CAKCAbMj-ck4qkuOaAbFHvFGWVWO-F2Knqj6rzTwsjib9QaVqhg@mail.gmail.com> (raw)
In-Reply-To: <42b1e1e9-6c29-4ee8-3fc7-ab220e217908@synopsys.com>
On Tue, Jun 27, 2017 at 12:40 PM, Vineet Gupta
<Vineet.Gupta1@synopsys.com> wrote:
> On 06/27/2017 02:47 PM, Joseph Myers wrote:
>>
>> longlong.h should be kept in sync with GCC. If the GCC version has been
>> fixed we can copy the updated version verbatim from GCC.
>
>
> Indeed it is fixed in upstream gcc.
>
> commit 608e1e3746f5242f0b0987ce64ca99969c33fb48
> Author: claziss <claziss@138bc75d-0d04-0410-961f-82ee72b054a4>
> Date: Fri Apr 29 10:11:25 2016 +0000
>
> [ARC] Fix obsolete constrain
>
> So I drop this patch from my series and rely on glibc upstream to have this
> fixed ?
Don't drop the patch; replace it with a patch that copies the file
verbatim from the GCC source tree.
zw
next prev parent reply other threads:[~2017-06-27 16:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 8:01 [RFC 0/6] glibc port to ARC architecture Vineet Gupta
2017-06-27 8:01 ` [RFC 6/6] ARC: Fix several testsuite failures related to unwinding Vineet Gupta
2017-06-27 8:01 ` [RFC 3/6] ARC: add definitions to elf/elf.h Vineet Gupta
2017-06-27 8:01 ` [RFC 1/6] upstream: comment update Vineet Gupta
2017-06-27 8:01 ` [RFC 5/6] ARC: Enable __start as entry point vs. canonical _start Vineet Gupta
2017-06-27 8:01 ` [RFC 2/6] ARC: Fixed inline asm contraints to gcc 6.x Vineet Gupta
2017-06-27 11:47 ` Joseph Myers
2017-06-27 16:40 ` Vineet Gupta
2017-06-27 16:54 ` Zack Weinberg [this message]
2017-06-27 8:02 ` [RFC 4/6] ARC: Initial port to glibc Vineet Gupta
2017-06-27 11:30 ` Florian Weimer
2017-06-27 11:55 ` Vineet Gupta
2017-06-27 12:01 ` Florian Weimer
2017-06-27 12:03 ` Joseph Myers
2017-06-27 11:56 ` Joseph Myers
2017-06-27 15:51 ` Vineet Gupta
2017-06-27 15:55 ` Joseph Myers
2017-06-27 16:52 ` Vineet Gupta
2017-06-27 17:02 ` Joseph Myers
2017-06-27 19:32 ` Vineet Gupta
2017-06-27 19:56 ` Joseph Myers
2017-06-28 8:49 ` ucontect vs. ucontext_t (was Re: [RFC 4/6] ARC: Initial port to glibc) Vineet Gupta
2017-06-28 9:23 ` Szabolcs Nagy
2017-06-28 9:30 ` Joseph Myers
2017-06-28 9:42 ` Vineet Gupta
2017-06-29 15:22 ` [RFC 4/6] ARC: Initial port to glibc Vineet Gupta
2017-06-29 15:29 ` Joseph Myers
2017-11-06 20:19 ` Vineet Gupta
2017-11-06 22:27 ` Joseph Myers
2017-06-27 11:31 ` [RFC 0/6] glibc port to ARC architecture Florian Weimer
2017-06-27 12:00 ` Joseph Myers
2017-11-06 22:52 ` Vineet Gupta
2017-11-06 23:09 ` Joseph Myers
2017-11-27 20:37 ` Vineet Gupta
2017-11-27 22:16 ` Joseph Myers
2017-12-08 0:31 ` Vineet Gupta
2017-12-08 11:15 ` Joseph Myers
2017-06-27 11:45 ` Joseph Myers
2017-06-27 13:16 ` Vineet Gupta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKCAbMj-ck4qkuOaAbFHvFGWVWO-F2Knqj6rzTwsjib9QaVqhg@mail.gmail.com \
--to=zackw@panix.com \
--cc=Cupertino.Miranda@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-snps-arc@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).