public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104010] [12 regression] short loop no longer vectorized with Neon after r12-3362
Date: Wed, 13 Apr 2022 10:43:51 +0000	[thread overview]
Message-ID: <bug-104010-4-p1mPg28TKs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104010-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Options to reproduce on arm-none-eabi:

-O3 -mcpu=cortex-a9 -mfpu=neon-fp16 -mfloat-abi=hard -o - vect.c -S
-fdump-tree-all-details

  parent reply	other threads:[~2022-04-13 10:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 15:52 [Bug tree-optimization/104010] New: [12 regression] short loop no longer vectorized with Neon after r12-6513 clyon at gcc dot gnu.org
2022-01-13 15:56 ` [Bug tree-optimization/104010] " pinskia at gcc dot gnu.org
2022-01-13 16:00 ` clyon at gcc dot gnu.org
2022-01-14  7:58 ` [Bug tree-optimization/104010] [12 regression] short loop no longer vectorized with Neon after r12-3362 rguenth at gcc dot gnu.org
2022-01-14  8:19 ` rguenth at gcc dot gnu.org
2022-01-14  8:35 ` rguenth at gcc dot gnu.org
2022-01-14  9:11 ` rguenth at gcc dot gnu.org
2022-04-13 10:42 ` rearnsha at gcc dot gnu.org
2022-04-13 10:43 ` rearnsha at gcc dot gnu.org [this message]
2022-04-13 11:36 ` rguenth at gcc dot gnu.org
2022-04-13 11:37 ` rguenth at gcc dot gnu.org
2022-04-13 11:38 ` rguenth at gcc dot gnu.org
2022-04-13 11:52 ` rguenth at gcc dot gnu.org
2022-04-13 13:12 ` clyon at gcc dot gnu.org
2022-04-14 11:30 ` rguenth at gcc dot gnu.org
2022-04-14 11:31 ` rguenth at gcc dot gnu.org
2022-04-19 14:42 ` cvs-commit at gcc dot gnu.org
2022-04-19 14:43 ` rguenth 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-104010-4-p1mPg28TKs@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).