From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: Jeff Law <law@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH][combine] Check WORD_REGISTER_OPERATIONS normally rather than through preprocessor
Date: Mon, 18 Apr 2016 09:33:00 -0000 [thread overview]
Message-ID: <5714A9E3.7060106@foss.arm.com> (raw)
In-Reply-To: <5713EF1B.1040706@redhat.com>
Hi Jeff,
On 17/04/16 21:16, Jeff Law wrote:
> On 12/15/2015 10:07 AM, Kyrill Tkachov wrote:
>> Hi all,
>>
>> As part of the war on conditional compilation here's an #if check on
>> WORD_REGISTER_OPERATIONS that
>> seems to have been missed out.
>>
>> Bootstrapped and tested on arm, aarch64, x86_64.
>>
>> Is it still ok to commit these kinds of conditional compilation
>> conversions?
>>
>> Thanks,
>> Kyrill
>>
>> 2015-12-15 Kyrylo Tkachov <kyrylo.tkachov@arm.com>
>>
>> * combine.c (simplify_comparison): Convert preprocessor check of
>> WORD_REGISTER_OPERATIONS into runtime check.
> This patch, and others like it are fine for the trunk (gcc-7) again.
>
Thanks, but I've committed this already in December after approval from Segher
(https://gcc.gnu.org/ml/gcc-patches/2015-12/msg01771.html)
> I'll channel the release managers' request that we don't make large scale changes that would make backporting patches exceedingly difficult. So just keep that in mind if you find more conditionally compiled code to kill.
>
I do have some cleanups like that, but I'll post them after the release. I'm in no hurry to get
them in right this moment.
Thanks,
Kyrill
> jeff
next prev parent reply other threads:[~2016-04-18 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 17:07 Kyrill Tkachov
2015-12-17 14:49 ` Segher Boessenkool
2015-12-22 10:39 ` Kyrill Tkachov
2016-04-17 21:25 ` Jeff Law
2016-04-18 9:33 ` Kyrill Tkachov [this message]
2016-04-21 11:37 ` Jeff Law
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=5714A9E3.7060106@foss.arm.com \
--to=kyrylo.tkachov@foss.arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=segher@kernel.crashing.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).