This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/42199] A problem with -maltivec
- From: "egallager at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 01 Aug 2017 18:27:41 +0000
- Subject: [Bug target/42199] A problem with -maltivec
- Auto-submitted: auto-generated
- References: <bug-42199-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42199
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
CC| |egallager at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Rafał Mużyło from comment #3)
> There's new input in a different Gentoo bug:
> http://bugs.gentoo.org/show_bug.cgi?id=305333
>
> Apparently in certain conditions on ppc,
> bool is both defined and undefined.
>
> Unless you'll see that as bad code on openjpeg side.
Yeah, bad code on the openjpeg side. Plus it's possible to trigger errors even
without -maltivec, so -maltivec is not the problem. Closing.