public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/37759] powerpc option -mabi=no-spe still generates SPE instructions
       [not found] <bug-37759-4@http.gcc.gnu.org/bugzilla/>
@ 2020-06-02  1:48 ` egallager at gcc dot gnu.org
  2020-06-02 23:47 ` segher at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: egallager at gcc dot gnu.org @ 2020-06-02  1:48 UTC (permalink / raw)
  To: gcc-bugs

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

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX
                 CC|                            |egallager at gcc dot gnu.org

--- Comment #11 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #10)
> (In reply to Arseny Solokha from comment #9)
> > Yes, but AFAIK none of the PRs specific to powerpcspe have been closed so
> > far. And, personally, I'd like them to stay open for another release cycle
> > in the hope Andrew would actually revive the target this year. But it's up
> > to gcc maintainers to decide, of course.
> 
> OK, leaving this open then...

The consensus here seemed to be to close them:
https://gcc.gnu.org/pipermail/gcc/2020-May/232591.html

So, I'm closing this.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug target/37759] powerpc option -mabi=no-spe still generates SPE instructions
       [not found] <bug-37759-4@http.gcc.gnu.org/bugzilla/>
  2020-06-02  1:48 ` [Bug target/37759] powerpc option -mabi=no-spe still generates SPE instructions egallager at gcc dot gnu.org
@ 2020-06-02 23:47 ` segher at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: segher at gcc dot gnu.org @ 2020-06-02 23:47 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #12 from Segher Boessenkool <segher at gcc dot gnu.org> ---
The powerpcspe backend has been deprecated in GCC 8 and removed during GCC 9
development. See corresponding mailing list threads[1,2,3] for details.

[1] https://gcc.gnu.org/legacy-ml/gcc/2018-04/msg00102.html
[2] https://gcc.gnu.org/legacy-ml/gcc-patches/2018-12/msg00123.html
[3] https://gcc.gnu.org/pipermail/gcc/2020-May/232342.html

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug target/37759] powerpc option -mabi=no-spe still generates SPE instructions
  2008-10-07  5:07 [Bug target/37759] New: powerpc option -mno-spe " patrick at motec dot com dot au
@ 2008-10-07 23:01 ` patrick at motec dot com dot au
  0 siblings, 0 replies; 3+ messages in thread
From: patrick at motec dot com dot au @ 2008-10-07 23:01 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #5 from patrick at motec dot com dot au  2008-10-07 23:00 -------
This looks like an option parsing problem.

Building with the deprecated -mspe=no option suppresses all SPE instructions,
which is what I expect/want. There seems to be no need to specify -mabi=no-spe
if -mspe=no is set.

-mno-spe seems to be broken.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37759


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-06-02 23:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-37759-4@http.gcc.gnu.org/bugzilla/>
2020-06-02  1:48 ` [Bug target/37759] powerpc option -mabi=no-spe still generates SPE instructions egallager at gcc dot gnu.org
2020-06-02 23:47 ` segher at gcc dot gnu.org
2008-10-07  5:07 [Bug target/37759] New: powerpc option -mno-spe " patrick at motec dot com dot au
2008-10-07 23:01 ` [Bug target/37759] powerpc option -mabi=no-spe " patrick at motec dot com dot au

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).