public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: "Martin Liška" <mliska@suse.cz>,
	"Richard Biener" <richard.guenther@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>, Michael Matz <matz@suse.de>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Optimize macro: make it more predictable
Date: Sat, 18 Sep 2021 23:46:30 -0600	[thread overview]
Message-ID: <8f0e9c8e-c6f7-bce9-51dc-ccd126bcfb36@gmail.com> (raw)
In-Reply-To: <6179ac10-8d2c-d0d5-21f4-0b6678fc8592@suse.cz>



On 9/13/2021 7:52 AM, Martin Liška wrote:
> On 8/27/21 11:05, Richard Biener wrote:
>> So with ignoring darktable which seems completely insane the cases
>> will likely continue
>> to work as intended if we change from the current scheme to appending
>> as proposed.
>
> All right, I'm addressing the flag_complex_method in a separate 
> sub-thread.
>
> There's slightly updated version of the patch where I modifed the 
> documentation bits.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
>
> 0001-Append-target-optimize-attr-to-the-current-cmdline.patch
>
>  From e13e3ec56acfb62543bc1912f1310d00eefba5c3 Mon Sep 17 00:00:00 2001
> From: Martin Liska <mliska@suse.cz>
> Date: Wed, 2 Jun 2021 08:44:37 +0200
> Subject: [PATCH] Append target/optimize attr to the current cmdline.
>
> gcc/c-family/ChangeLog:
>
> 	* c-common.c (parse_optimize_options): Combine optimize
> 	options with what was provided on the command line.
>
> gcc/ChangeLog:
>
> 	* toplev.c (toplev::main): Save decoded optimization options.
> 	* toplev.h (save_opt_decoded_options): New.
> 	* doc/extend.texi: Be more clear about optimize and target
> 	attributes.
>
> gcc/testsuite/ChangeLog:
>
> 	* gcc.target/i386/avx512er-vrsqrt28ps-3.c: Disable fast math.
> 	* gcc.target/i386/avx512er-vrsqrt28ps-5.c: Likewise.
> 	* gcc.target/i386/attr-optimize.c: New test.
OK
jeff


  reply	other threads:[~2021-09-19  5:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 11:47 Martin Liška
2020-11-03 13:27 ` Richard Biener
2020-11-03 13:34   ` Jakub Jelinek
2020-11-03 13:40     ` Richard Biener
2020-11-09 10:35     ` Martin Liška
2020-11-26 13:56       ` Martin Liška
2020-12-07 11:03         ` Martin Liška
2021-01-11 13:10           ` Martin Liška
2020-11-09 10:27   ` Martin Liška
2020-11-06 17:34 ` Jeff Law
2020-11-09 10:36   ` Martin Liška
2021-07-01 13:13 ` Martin Liška
2021-08-10 15:52   ` Martin Liška
2021-08-24 11:06     ` Martin Liška
2021-08-24 12:13   ` Richard Biener
2021-08-24 13:04     ` Martin Liška
2021-08-26 11:04       ` Richard Biener
2021-08-26 12:39         ` Martin Liška
2021-08-26 13:20           ` Richard Biener
2021-08-27  8:35           ` Martin Liška
2021-08-27  9:05             ` Richard Biener
2021-09-13 13:52               ` Martin Liška
2021-09-19  5:46                 ` Jeff Law [this message]
2021-09-06 11:37         ` [PATCH] flag_complex_method: support optimize attribute Martin Liška
2021-09-06 11:46           ` Jakub Jelinek
2021-09-06 12:16             ` Richard Biener
2021-09-06 12:24               ` Jakub Jelinek
2021-09-07  9:42               ` Martin Liška
2021-09-13 13:32                 ` Martin Liška
2021-09-19 14:45                 ` 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=8f0e9c8e-c6f7-bce9-51dc-ccd126bcfb36@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=matz@suse.de \
    --cc=mliska@suse.cz \
    --cc=richard.guenther@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).