From: Richard Biener <richard.guenther@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, ismail@donmez.ws
Subject: Re: [PATCH] Fix PR bootstrap/66471
Date: Tue, 09 Jun 2015 13:29:00 -0000 [thread overview]
Message-ID: <CAFiYyc3cJNiyZMufB+1_cn-c0ATd3MD4J+TiRPx5w-=EL9J6yQ@mail.gmail.com> (raw)
In-Reply-To: <5576E606.1060407@suse.cz>
On Tue, Jun 9, 2015 at 3:11 PM, Martin Liška <mliska@suse.cz> wrote:
> Hello.
>
> Following patch renames an enum values so that they do not clash with a MinGW reserved keyword.
Reserved keyword as in a #define? Thus simply #undef it in system.h?
> Patch can bootstrap on MinGW and there's no regression seen on x86_64-linux-unknown-gnu.
Does c++04 have scoped enums? Thus can you use mem_alloc_origin::BITMAP?
Thanks,
Richard.
> Ready for trunk?
> Thanks,
> Martin
next prev parent reply other threads:[~2015-06-09 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 13:21 Martin Liška
2015-06-09 13:29 ` Richard Biener [this message]
2015-06-09 13:35 ` İsmail Dönmez
2015-06-09 13:39 ` Richard Biener
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='CAFiYyc3cJNiyZMufB+1_cn-c0ATd3MD4J+TiRPx5w-=EL9J6yQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ismail@donmez.ws \
--cc=mliska@suse.cz \
/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).