From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
Dodji Seketeli <dodji@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 3/6] Emit macro expansion related diagnostics
Date: Tue, 18 Oct 2011 15:37:00 -0000 [thread overview]
Message-ID: <CAAiZkiB8RD7cSXEjTCNbuqpQr+pgw0bEeeFSJ4JGjz1NAhKNxw@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1110181516120.24292@digraph.polyomino.org.uk>
On Tue, Oct 18, 2011 at 10:19 AM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> On Tue, 18 Oct 2011, David Edelsohn wrote:
>
>> Hey, Dodji,
>>
>> Your patch broke bootstrap on AIX because of the typedef "loc_t"
>> introduced in tree-diagnostics.c. The typedef conflicts with a
>> typedef in an AIX 5.3 header file for locales. AIX should not be
>> using that namespace, but the failure occurs before fix-includes, so
>> it is not possible to fix it there.
>
> The whole *_t namespace is reserved by POSIX, so it's not unreasonable for
> AIX to have some AIX-specific *_t typedefs although it seems quite rare
> for this to cause conflicts in practice (and AIX is obviously risking
> conflicts with future POSIX revisions by using *_t for its own types).
any reason we could not call it location_type? or just location?
next prev parent reply other threads:[~2011-10-18 15:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 15:25 David Edelsohn
2011-10-18 15:30 ` Joseph S. Myers
2011-10-18 15:37 ` Gabriel Dos Reis [this message]
2011-10-18 15:34 ` Jakub Jelinek
2011-10-18 16:56 ` Dodji Seketeli
2011-10-18 18:16 ` Dodji Seketeli
-- strict thread matches above, loose matches on Subject: below --
2011-10-17 9:58 [PATCH 0/6] Tracking locations of tokens resulting from macro expansion Dodji Seketeli
2011-10-17 9:58 ` [PATCH 3/6] Emit macro expansion related diagnostics Dodji Seketeli
2011-10-17 10:56 ` Richard Guenther
2011-10-17 12:22 ` Dodji Seketeli
2011-10-17 14:11 ` Dodji Seketeli
2011-10-17 17:41 ` H.J. Lu
2011-10-18 0:29 ` Dodji Seketeli
2011-10-18 6:07 ` Jason Merrill
2011-10-18 9:22 ` Dodji Seketeli
2010-12-10 11:27 [PATCH 0/6] Tracking locations of tokens resulting from macro expansion Dodji Seketeli
2010-12-10 11:27 ` [PATCH 3/6] Emit macro expansion related diagnostics Dodji Seketeli
2010-12-13 15:25 ` Paolo Bonzini
2010-12-13 15:38 ` Paolo Bonzini
2010-12-13 16:30 ` Manuel López-Ibáñez
2010-12-14 7:24 ` Dodji Seketeli
2010-12-14 7:28 ` Gabriel Dos Reis
2010-12-14 8:40 ` Dodji Seketeli
2010-12-14 9:38 ` Gabriel Dos Reis
2010-12-14 9:42 ` Dodji Seketeli
2010-12-14 9:48 ` Gabriel Dos Reis
2010-12-14 7:28 ` Dodji Seketeli
2010-12-14 8:19 ` Gabriel Dos Reis
2010-12-14 8:31 ` Paolo Bonzini
2010-12-14 9:23 ` Dodji Seketeli
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=CAAiZkiB8RD7cSXEjTCNbuqpQr+pgw0bEeeFSJ4JGjz1NAhKNxw@mail.gmail.com \
--to=gdr@integrable-solutions.net \
--cc=dje.gcc@gmail.com \
--cc=dodji@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
/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).