public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: "augustine.sterling@gmail.com" <augustine.sterling@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
		"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>
Subject: Re: [RFC 1/5] gcc: xtensa: allow XCHAL_* macros to be non-constant
Date: Wed, 14 Jun 2017 17:23:00 -0000	[thread overview]
Message-ID: <CAMo8Bf+iAt-F0Brcyz5CBYc1KDojbGSfLwOA5NMEPwObui4O8g@mail.gmail.com> (raw)
In-Reply-To: <CAGSvup9rwqrhcMfUEdED0ytda1_0G2e3+VacfsvJJ105FYFgzg@mail.gmail.com>

On Thu, May 25, 2017 at 11:15 AM, augustine.sterling@gmail.com
<augustine.sterling@gmail.com> wrote:
> On Mon, May 22, 2017 at 2:09 PM, Max Filippov <jcmvbkbc@gmail.com> wrote:
>> XCHAL_* macros from the xtensa-config.h are used in a number of places
>> that require them to be preprocessor constants. Rewrite these places so
>> that non-constant XCHAL_* definitions could be used there.
>>
>> 2017-05-22  Max Filippov  <jcmvbkbc@gmail.com>
>> gcc/
>>         * config/xtensa/xtensa.c (xtensa_option_override): Append
>>         MASK_CONST16 to target_flags in the absence of TARGET_L32R.
>>         (hwloop_optimize, hwloop_fail, hwloop_pattern_reg,
>>          xtensa_doloop_hooks): Define unconditionally.
>>         (xtensa_reorg_loops): Only call reorg_loops in the presence of
>>         TARGET_LOOPS.
>>         * config/xtensa/xtensa.h (TARGET_L32R): New definition.
>>         (TARGET_DEFAULT): Remove XCHAL_HAVE_L32R condition and account
>>         for it in xtensa_option_override.
>>         (HARD_FRAME_POINTER_IS_FRAME_POINTER,
>>          HARD_FRAME_POINTER_IS_ARG_POINTER): New definitions.
>
> This is OK. Please apply.

Applied this one to trunk. Thanks!

-- Max

      reply	other threads:[~2017-06-14 17:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 21:09 [RFC 0/5] xtensa: support dynamic configuration Max Filippov
2017-05-22 21:09 ` [RFC 3/5] gcc: xtensa: support dynconfig on windows Max Filippov
2017-05-22 21:09 ` [RFC 4/5] gcc: xtensa: add __XCHAL_* builtins Max Filippov
2017-05-22 21:09 ` [RFC 5/5] libgcc: xtensa: use built-in configuration Max Filippov
2017-05-22 21:09 ` [RFC 2/5] gcc: xtensa: make configuration dynamic Max Filippov
2017-05-25 18:25   ` augustine.sterling
2017-05-25 20:57     ` Max Filippov
2017-05-26 15:04       ` Ian Lance Taylor via gcc-patches
2017-05-26 18:48         ` Max Filippov
2017-05-22 21:31 ` [RFC 1/5] gcc: xtensa: allow XCHAL_* macros to be non-constant Max Filippov
2017-05-22 21:49   ` augustine.sterling
2017-05-23  2:19     ` Max Filippov
2017-05-25 18:24   ` augustine.sterling
2017-06-14 17:23     ` Max Filippov [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=CAMo8Bf+iAt-F0Brcyz5CBYc1KDojbGSfLwOA5NMEPwObui4O8g@mail.gmail.com \
    --to=jcmvbkbc@gmail.com \
    --cc=augustine.sterling@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=linux-xtensa@linux-xtensa.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).