From: Ian Lance Taylor <iant@google.com>
To: Patrick Wollgast <patrick.wollgast@rub.de>
Cc: Kai Tietz <ktietz70@googlemail.com>,
"cmtice@google.com >> Caroline Tice" <cmtice@google.com>,
bkoz@gnu.org,
"jwakely@redhat.com >> Jonathan Wakely" <jwakely@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Re: [Ping] Port of VTV for Cygwin and MinGW
Date: Wed, 14 Jan 2015 23:56:00 -0000 [thread overview]
Message-ID: <CAKOQZ8w9_5OJEfnWJ-rgBgVzOzQcEj984MQcp=R1w=0JLUU8mw@mail.gmail.com> (raw)
In-Reply-To: <54B6D159.4000002@rub.de>
On Wed, Jan 14, 2015 at 12:28 PM, Patrick Wollgast
<patrick.wollgast@rub.de> wrote:
> On 14.01.2015 20:00, Ian Lance Taylor wrote:
>> On Thu, Jan 8, 2015 at 12:33 PM, Patrick Wollgast
>> <patrick.wollgast@rub.de> wrote:
>>> A short recap again:
>>>
>>> Latest patch, changelog and a test program (further information about
>>> the program in the mail):
>>> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg03368.html
>>
>> In that patch, the change to varasm.c looks wrong if neither
>> OBJECT_FORMAT_ELF nor TARGET_PECOFF are defined. It looks like you've
>> dropped the switch_to_section call in that case.
>>
>> Ian
>>
>
> You're right. It should have been '#else' again, instead of 'else'
> before the switch_to_section call.
OK, the patches to varasm.c and cp/vtable-class-hierarchy.c are OK.
Thanks.
Ian
next prev parent reply other threads:[~2015-01-14 23:52 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 11:04 Patrick Wollgast
2014-09-11 4:12 ` [Ping] " Patrick Wollgast
[not found] ` <CABtf2+RU7frwOXOX2FF8Tmfc6ssrpfFVj1Vuue4cZt19FpSWtQ@mail.gmail.com>
2014-09-12 22:44 ` Caroline Tice
2014-09-18 22:24 ` Patrick Wollgast
2014-09-23 6:16 ` Caroline Tice
2014-09-23 10:22 ` Jonathan Wakely
2014-09-24 22:25 ` Patrick Wollgast
2014-09-27 10:50 ` Kai Tietz
2014-10-09 13:56 ` Patrick Wollgast
2014-10-09 14:47 ` Kai Tietz
2014-10-16 10:23 ` Patrick Wollgast
2014-10-30 14:51 ` Patrick Wollgast
2014-11-12 16:23 ` Patrick Wollgast
2014-11-12 17:05 ` Kai Tietz
2014-11-12 17:47 ` Patrick Wollgast
2014-11-12 18:45 ` Kai Tietz
2014-11-27 9:59 ` Patrick Wollgast
2014-12-10 16:37 ` Patrick Wollgast
2015-01-04 20:10 ` Patrick Wollgast
2015-01-08 20:34 ` Patrick Wollgast
2015-01-12 18:32 ` Caroline Tice
2015-01-14 19:28 ` Ian Lance Taylor
2015-01-14 21:23 ` Patrick Wollgast
2015-01-14 23:56 ` Ian Lance Taylor [this message]
2015-01-15 8:34 ` Patrick Wollgast
2015-01-15 16:14 ` Ian Lance Taylor
2015-01-15 22:13 ` Patrick Wollgast
2015-01-28 14:04 ` Patrick Wollgast
2015-01-29 1:58 ` Caroline Tice
2015-01-29 18:16 ` Matthias Klose
2015-01-29 18:26 ` Matthias Klose
2015-01-29 18:28 ` Jonathan Wakely
2015-01-29 18:34 ` H.J. Lu
2015-01-29 18:59 ` H.J. Lu
2015-01-29 19:27 ` H.J. Lu
2015-01-29 18:30 ` H.J. Lu
2015-01-29 18:53 ` Matthias Klose
2015-01-29 19:39 ` Jakub Jelinek
2015-01-29 19:55 ` H.J. Lu
2015-01-29 20:01 ` Jakub Jelinek
2015-01-29 20:08 ` H.J. Lu
2015-01-29 19:28 ` Jakub Jelinek
2015-01-29 18:16 ` H.J. Lu
2015-01-29 18:22 ` H.J. Lu
2015-01-29 18:23 ` Caroline Tice
2015-02-09 12:32 ` Thomas Schwinge
2015-02-02 19:56 ` Patrick Wollgast
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='CAKOQZ8w9_5OJEfnWJ-rgBgVzOzQcEj984MQcp=R1w=0JLUU8mw@mail.gmail.com' \
--to=iant@google.com \
--cc=bkoz@gnu.org \
--cc=cmtice@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=ktietz70@googlemail.com \
--cc=libstdc++@gcc.gnu.org \
--cc=patrick.wollgast@rub.de \
/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).