From: Richard Biener <richard.guenther@gmail.com>
To: NightStrike <nightstrike@gmail.com>
Cc: Kai Tietz <ktietz70@googlemail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch print-tree.c]: 5 of 7 Fix of PR target/53912 bootstrap fails using default c++ mode in stage 2 and 3 for native x86_64-w64-mingw32
Date: Mon, 10 Dec 2012 09:21:00 -0000 [thread overview]
Message-ID: <CAFiYyc08PTTP5b+8-bzXjE4+1dErSXGG4cWo=2AaQMPZhz2iJQ@mail.gmail.com> (raw)
In-Reply-To: <CAF1jjLu5EnAEe=o=Wg+dEnn8Syjn+zh+gski41L-5sX8LPQbJA@mail.gmail.com>
On Sun, Dec 9, 2012 at 5:18 PM, NightStrike <nightstrike@gmail.com> wrote:
> On Sat, Dec 1, 2012 at 11:12 PM, Kai Tietz <ktietz70@googlemail.com> wrote:
>> Ping
>>
>> 2012/11/29 Kai Tietz <ktietz70@googlemail.com>:
>>> Hello,
>>>
>>> this trivial patch fixes a bootstrap issue on LLP64 hosts.
>>>
>>> ChangeLog
>>>
>>> 2012-11-29 Kai Tietz
>>>
>>> PR target/53912
>>> * print-tree.c (print_node): Cast from pointer via uintptr_t.
>>>
>>> Tested for i686-w64-mingw32, x86_64-w64-mingw32, and
>>> x86_64-unknown-gnu-linux. Ok for apply?
>>>
>>> Regards,
>>> Kai
>>>
>>> Index: print-tree.c
>>> ===================================================================
>>> --- print-tree.c (Revision 193925)
>>> +++ print-tree.c (Arbeitskopie)
>>> @@ -255,7 +255,7 @@ print_node (FILE *file, const char *prefix, tree n
>>> /* Allow this function to be called if the table is not there. */
>>> if (table)
>>> {
>>> - hash = ((unsigned long) node) % HASH_SIZE;
>>> + hash = ((uintptr_t) node) % HASH_SIZE;
>>>
>>> /* If node is in the table, just mention its address. */
>>> for (b = table[hash]; b; b = b->next)
>
> Ping.
Ok.
Thanks,
Richard.
prev parent reply other threads:[~2012-12-10 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 12:11 Kai Tietz
2012-12-02 9:12 ` Kai Tietz
2012-12-09 16:18 ` NightStrike
2012-12-10 9:21 ` Richard Biener [this message]
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='CAFiYyc08PTTP5b+8-bzXjE4+1dErSXGG4cWo=2AaQMPZhz2iJQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ktietz70@googlemail.com \
--cc=nightstrike@gmail.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).