[Bug testsuite/101528] [11 regression] gcc.target/powerpc/int_128bit-runnable.c fails after r11-8743

2023-05-22 Thread cel at us dot ibm.com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101528 --- Comment #7 from Carl Love --- I recently committed a patch to fix the counts. commit 5d336ae49528fde3904c9e5bfc83a450429b2961 Author: Carl Love Date: Fri Mar 10 18:16:52 2023 -0500 rs6000: Fix test int_128bit-runnable.c instruction

[Bug testsuite/101528] [11 regression] gcc.target/powerpc/int_128bit-runnable.c fails after r11-8743

2023-05-19 Thread cel at us dot ibm.com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101528 Carl Love changed: What|Removed |Added CC||cel at us dot ibm.com --- Comment #6 from

[Bug c/108996] New: Proposal for adding DWARF call site information got GCC with -O0

2023-03-02 Thread cel at us dot ibm.com via Gcc-bugs
Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: cel at us dot ibm.com Target Milestone: --- On PowerPC, the address of the buffer to return non-trivial values such as structures is passed in register r3. The value of r3 on entry

[Bug target/101022] rs6000: __builtin_altivec_vcmpequt expands to wrong pattern

2021-06-10 Thread cel at us dot ibm.com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101022 Carl Love changed: What|Removed |Added CC||cel at us dot ibm.com --- Comment #3 from

[Bug target/98092] [11 Regression] ICE in extract_insn, at recog.c:2315 (error: unrecognizable insn)

2021-01-22 Thread cel at us dot ibm.com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98092 --- Comment #2 from Carl Love --- Segher: Yup, I saw the buzilla. Will take a look at it. Carl On Fri, 2021-01-22 at 18:49 +, segher at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98092 > >

[Bug target/93449] PPC: Missing conversion builtin from vector to _Decimal128 and vice versa

2020-11-02 Thread cel at us dot ibm.com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93449 Carl Love changed: What|Removed |Added CC||cel at us dot ibm.com --- Comment #10 from

[Bug target/85830] vec_popcntd is improperly defined in altivec.h

2020-08-27 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85830 --- Comment #4 from Carl Love --- Just remove #define vec_popcntb __builtin_vec_vpopcntub #define vec_popcnth __builtin_vec_vpopcntuh #define vec_popcntw __builtin_vec_vpopcntuw #define vec_popcntd __builtin_vec_vpopcntud from

[Bug target/85830] vec_popcntd is improperly defined in altivec.h

2020-08-27 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85830 --- Comment #2 from Carl Love --- Hit the save button a little too fast missed putting in everything I intended to put in. Lets try to get it all in. (In reply to Carl Love from comment #1) > The Power 64-Bi ELF V2 ABI specification revision

[Bug target/85830] vec_popcntd is improperly defined in altivec.h

2020-08-27 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85830 Carl Love changed: What|Removed |Added CC||cel at us dot ibm.com --- Comment #1 from

[Bug target/93819] PPC64 builtin vec_rlnm() argument order is wrong.

2020-03-31 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93819 Carl Love changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #8 from Carl Love ---

[Bug target/93819] PPC64 builtin vec_rlnm() argument order is wrong.

2020-03-31 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93819 Carl Love changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug target/91638] powerpc -mlong-double-NN (documentation) issues

2020-03-09 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91638 Carl Love changed: What|Removed |Added CC||cel at us dot ibm.com --- Comment #7 from

[Bug target/91638] powerpc -mlong-double-NN (documentation) issues

2020-03-06 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91638 --- Comment #6 from Carl Love --- Yea, I like that a bit better. It is a bit shorter, mine was a bit verbose. I updated the patch to print: -mlong-double- Use -mlong-double-64 for 64-bit IEEE floating

[Bug target/91638] powerpc -mlong-double-NN (documentation) issues

2020-03-05 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91638 --- Comment #4 from Carl Love --- Created attachment 47982 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47982=edit patch to update -mlong-double-NN description Attached the proposed patch so I will not lose it.

[Bug target/91638] powerpc -mlong-double-NN (documentation) issues

2020-03-05 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91638 Carl Love changed: What|Removed |Added CC||cel at us dot ibm.com --- Comment #3 from

[Bug c/93819] PPC64 builtin vec_rlnm() argument order is wrong.

2020-02-18 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93819 --- Comment #2 from Carl Love --- With the attached patch, the test program now runs as follows: ABI says: VEC_RLNM (ARG1, ARG2, ARG3) ARG2 contains the shift count for each element in the low-order byte, with other bytes zero. ARG3 contains

[Bug c/93819] PPC64 builtin vec_rlnm() argument order is wrong.

2020-02-18 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93819 --- Comment #1 from Carl Love --- Created attachment 47873 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47873=edit Patch to fix vec_vrlnm() functionality The issue with the vec_rlnm() builtin is the order of the arguments in the builtin

[Bug c/93819] New: PPC64 builtin vec_rlnm() argument order is wrong.

2020-02-18 Thread cel at us dot ibm.com
: c Assignee: unassigned at gcc dot gnu.org Reporter: cel at us dot ibm.com Target Milestone: --- Created attachment 47872 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47872=edit test program to demonstrate the bug. The API for the PPC 64 vec_rlnm() builtin s

[Bug debug/93206] non-delegitimized UNSPEC generated for C program on PowerPc with current mainline GCC tree

2020-01-09 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206 --- Comment #11 from Carl Love --- Created attachment 47626 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47626=edit 311r.dwarf2 file for v4si and the v2di test case The attached file was generated with the #if in the test program set to

[Bug debug/93206] non-delegitimized UNSPEC generated for C program on PowerPc with current mainline GCC tree

2020-01-09 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206 --- Comment #10 from Carl Love --- Created attachment 47625 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47625=edit 310r.nothrow for both tests v4si and v2di The attached file was generated with the #if in the test program set to 1 to

[Bug debug/93206] non-delegitimized UNSPEC generated for C program on PowerPc with current mainline GCC tree

2020-01-09 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206 --- Comment #9 from Carl Love --- Created attachment 47624 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47624=edit 311r.dwarf2 file for just the v2di test case The attached file was generated with the #if in the test program set to 0 so

[Bug debug/93206] non-delegitimized UNSPEC generated for C program on PowerPc with current mainline GCC tree

2020-01-09 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206 --- Comment #8 from Carl Love --- Created attachment 47623 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47623=edit 310r.nothrow for just the __builtin_vec_foo_v2di test case The attached file was generated with the #if in the test

[Bug debug/93206] non-delegitimized UNSPEC generated for C program on PowerPc with current mainline GCC tree

2020-01-09 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206 --- Comment #5 from Carl Love --- I am puzzled. When we have both test cases included which are identical other then the data size, the notes are correct for second test case but not the first test case. When we remove the first test case,

[Bug debug/93206] non-delegitimized UNSPEC generated for C program on PowerPc with current mainline GCC tree

2020-01-09 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206 --- Comment #3 from Carl Love --- The initial bug report states that the bug moves around depending on the test case. If the test case only consists of the test for the V2DI case, you get the error that Bill was specifically stating, i.e.

[Bug c/93206] New: non-delegitimized UNSPEC generated for C program on PowerPc with current mainline GCC tree

2020-01-08 Thread cel at us dot ibm.com
Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: cel at us dot ibm.com Target Milestone: --- Created attachment 47616 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47616=edit GCC src tree pa

[Bug target/84371] test case gcc.target/powerpc/builtins-3.c fails on power9

2018-02-19 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84371 --- Comment #2 from Carl Love --- Will: Here is the bug report I just got from Peter. From our sametime conversation sounds like you have addressed these in a recent update. Take a look, may be that Peter needs to update his tree

[Bug target/81158] [8 regression] Many test case failures starting with r249424

2017-06-22 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81158 --- Comment #2 from Carl Love --- On Thu, 2017-06-22 at 21:06 +, wschmidt at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81158 > > --- Comment #1 from Bill Schmidt --- > I expect this is probably due to the

[Bug target/79039] builtins-3-p9.c fails with -m32

2017-01-10 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79039 --- Comment #2 from Carl Love --- On Tue, 2017-01-10 at 14:29 +, wschmidt at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79039 > > Bill Schmidt changed: > >What|Removed |Added

[Bug target/68752] PowerPC: vector reciprocal square root estimate missed optimisations

2016-10-10 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68752 --- Comment #4 from Carl Love --- I do not seem to have permission to change the status of the bug. Anton, can you recheck the issue and close if you agree it is no longer an issue. Thanks. Carl

[Bug target/68752] PowerPC: vector reciprocal square root estimate missed optimisations

2016-10-10 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68752 --- Comment #3 from Carl Love --- I investigated the issue using GCC 6.1. The t1() function from file recip-vec-sqrtf.c file is as follows: void t1(void) { int i; for (i = 0; i < 4; i++) r[i] = a[i] / sqrtf (b[i]); } The assembly code being

[Bug target/68752] PowerPC: vector reciprocal square root estimate missed optimisations

2016-10-10 Thread cel at us dot ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68752 Carl Love changed: What|Removed |Added CC||cel at us dot ibm.com --- Comment #2 from