public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "piliu at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/105134] tree-vectorize produces error code
Date: Wed, 30 Nov 2022 03:32:50 +0000	[thread overview]
Message-ID: <bug-105134-4-PUYVIhH7ae@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105134-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from piliu at redhat dot com ---
(In reply to Andrew Pinski from comment #7)
> I am trying to understand this. Is it ok to use the SSE registers inside
> purgatory or not?
> 

SSE can speed up the program, and if possible it is suggested to turn on.

Any guideline about when it can not be used?

> Now that the vectorizer is used turned on at -O2 and above, without
> -mno-sse, on x86_64 target, the vector instructions are generated. and since
> this is inside a tiny bootloader, I am suspecting you can't use SSE
> instructions here.
> 

What is broken by SSE? That can be more persuaded.

Thanks,

Pingfan

  parent reply	other threads:[~2022-11-30  3:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-02  2:43 [Bug c/105134] New: " piliu at redhat dot com
2022-04-02  3:01 ` [Bug c/105134] " piliu at redhat dot com
2022-04-02  5:28 ` piliu at redhat dot com
2022-04-04  7:15 ` rguenth at gcc dot gnu.org
2022-04-06  2:12 ` piliu at redhat dot com
2022-04-06  2:14 ` piliu at redhat dot com
2022-04-06  2:17 ` piliu at redhat dot com
2022-11-25 22:53 ` pinskia at gcc dot gnu.org
2022-11-25 23:00 ` pinskia at gcc dot gnu.org
2022-11-25 23:03 ` pinskia at gcc dot gnu.org
2022-11-30  3:32 ` piliu at redhat dot com [this message]
2022-11-30  3:42 ` pinskia at gcc dot gnu.org
2024-02-21  0:40 ` [Bug tree-optimization/105134] " pinskia 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-105134-4-PUYVIhH7ae@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).