public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/101324] powerpc64le: hashst appears before mflr at -O1 or higher
Date: Mon, 25 Oct 2021 20:48:40 +0000	[thread overview]
Message-ID: <bug-101324-4-Qef7nIHyUW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101324-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101324

--- Comment #7 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #6)
> Heh, another example of __attribute__((optimize("..."))) problem:
> 
> __attribute__ ((__optimize__ ("-fno-tree-loop-distribute-patterns")))
> __memmove_ppc ( void *dest, const void *src, size_t len)
> {
> ...
> }
> 
> -mrop-protect is dropped when optimize attribute is parsed, for more
> information see:
> https://gcc.gnu.org/pipermail/gcc-patches/2021-August/577113.html

So what is the status with this?  IIUC, looking at the thread, it seems like
you and richi agreed that the optimize flags should be treated as if they were
appended to the command line, but that doesn't seem how trunk works right now. 
So does GCC still need fixing or is the test case using the attribute optimize
incorrectly or ???

  parent reply	other threads:[~2021-10-25 20:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 15:32 [Bug target/101324] New: " tuliom at ascii dot art.br
2021-07-05 22:18 ` [Bug target/101324] " segher at gcc dot gnu.org
2021-07-05 23:54 ` segher at gcc dot gnu.org
2021-07-06 13:28 ` segher at gcc dot gnu.org
2021-07-06 13:46 ` tuliom at ascii dot art.br
2021-07-12  3:41 ` marxin at gcc dot gnu.org
2021-08-12 16:17 ` marxin at gcc dot gnu.org
2021-08-16 11:37 ` marxin at gcc dot gnu.org
2021-10-25 16:54 ` marxin at gcc dot gnu.org
2021-10-25 20:48 ` bergner at gcc dot gnu.org [this message]
2021-10-25 20:49 ` bergner at gcc dot gnu.org
2021-10-26  6:02 ` marxin at gcc dot gnu.org
2021-10-26  6:26 ` marxin at gcc dot gnu.org
2021-10-26 11:35 ` bergner at gcc dot gnu.org
2021-10-26 11:42 ` bergner at gcc dot gnu.org
2021-10-26 14:43 ` marxin at gcc dot gnu.org
2021-10-26 15:32 ` bergner at gcc dot gnu.org
2021-10-26 16:55 ` segher at gcc dot gnu.org
2021-10-26 19:08 ` bergner at gcc dot gnu.org
2021-10-27 20:08 ` bergner at gcc dot gnu.org
2021-10-27 20:09 ` bergner at gcc dot gnu.org
2021-10-28  3:19 ` bergner at gcc dot gnu.org
2021-12-03 20:32 ` cvs-commit at gcc dot gnu.org
2021-12-03 20:43 ` bergner at gcc dot gnu.org
2021-12-03 21:29 ` bergner at gcc dot gnu.org
2021-12-03 22:36 ` bergner at gcc dot gnu.org
2021-12-27 13:50 ` raoni at linux dot ibm.com
2022-02-11 19:28 ` cvs-commit at gcc dot gnu.org
2022-02-11 22:33 ` bergner at gcc dot gnu.org
2024-06-18 23:07 ` bergner at gcc dot gnu.org

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=bug-101324-4-Qef7nIHyUW@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).