From: Joseph Myers <joseph@codesourcery.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "libc-alpha @ sourceware . org" <libc-alpha@sourceware.org>,
<linux-snps-arc@lists.infradead.org>,
<Cupertino.Miranda@synopsys.com>
Subject: Re: [RFC 4/6] ARC: Initial port to glibc
Date: Tue, 27 Jun 2017 15:55:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1706271553590.18823@digraph.polyomino.org.uk> (raw)
In-Reply-To: <0cd32bdd-5ec4-0fb6-8cf8-fd658596e790@synopsys.com>
On Tue, 27 Jun 2017, Vineet Gupta wrote:
> > > +typedef struct sigcontext mcontext_t;
> >
> > You can avoid this problematic definition for a new architecture, even
> > while we're still discussing eliminating it for existing architectures.
>
> So just use struct sigcontext as data type for uc_mcontext ?
No. Define mcontext_t to be a struct without a tag, with the same layout
as struct sigcontext, as the identifier sigcontext (and non-reserved
identifiers for its elements) are not in the POSIX namespace permitted for
ucontext.h.
https://sourceware.org/ml/libc-alpha/2017-06/msg00946.html
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-06-27 15:55 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 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
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 3/6] ARC: add definitions to elf/elf.h Vineet Gupta
2017-06-27 8:01 ` [RFC 6/6] ARC: Fix several testsuite failures related to unwinding Vineet Gupta
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 [this message]
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=alpine.DEB.2.20.1706271553590.18823@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Cupertino.Miranda@synopsys.com \
--cc=Vineet.Gupta1@synopsys.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).