https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98384
--- Comment #23 from David Edelsohn ---
The AIX failure is:
printf_buffer=
1.442695040888963387004650940070860088
to_chars_buffer=
1.442695040888963387004650940070860087871551513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98384
--- Comment #26 from David Edelsohn ---
By default, long double on AIX is the same as double (64 bits). One optionally
can specify 128 bit long double and link with libc128.a to provide long double
stdio.
AIX float.h:
#define DECIMAL_DIG
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99492
Bug ID: 99492
Summary: double and double _Complex not aligned consistently on
AIX
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94177
David Edelsohn changed:
What|Removed |Added
Last reconfirmed||2021-03-09
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99094
--- Comment #2 from David Edelsohn ---
GCC should place uninitialized static variables into a separate "section
anchor" pool.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99492
David Edelsohn changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99557
Bug ID: 99557
Summary: [AIX] Alignment of double for struct and C++ classes
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: ABI
Severity: normal
Priori
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99557
David Edelsohn changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99094
David Edelsohn changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99492
David Edelsohn changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99653
Bug ID: 99653
Summary: [AIX] Bitfield placement
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: ABI
Severity: normal
Priority: P3
Component: t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99653
David Edelsohn changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99718
--- Comment #8 from David Edelsohn ---
Xionghu, please do not write "can't" when you mean "it's difficult" or "it
hasn't been implemented" or "it's too inefficient" (such as moving the data
through memory). Please be very precise in your explana
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99718
David Edelsohn changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85907
--- Comment #4 from David Edelsohn ---
There still are problems because of the manner in which AIX statically links.
Normally AIX does not create separate archives of object files for static
linking; one statically links by statically linking ag
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100164
Bug ID: 100164
Summary: [11 Regression] semaphore_impl not declaredon AIX
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: blocker
Priority: P3
Compo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100164
David Edelsohn changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100164
--- Comment #6 from David Edelsohn ---
Created attachment 50644
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50644&action=edit
pre-processed source for 17_intro/headers/c++2020/all_attributes.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100164
--- Comment #8 from David Edelsohn ---
I am not certain why you cannot log in to the compile farm system.
I am testing the patch on one of the AIX systems inside IBM.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100164
--- Comment #9 from David Edelsohn ---
The previous semaphore_base.h implementation had a fallback that hid a bug in
the macros:
#if defined _GLIBCXX_HAVE_LINUX_FUTEX && !_GLIBCXX_REQUIRE_POSIX_SEMAPHORE
// Use futex if available and didn't f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100164
--- Comment #14 from David Edelsohn ---
Thanks for the patch. This now removes the failure that semaphore_impl is not
found.
Because the platform semaphore code never was exercised due to the bug in the
macro, there are more latent bugs.
/tmp/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100186
Bug ID: 100186
Summary: lto-wrapper.c assumes std::thread
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100186
David Edelsohn changed:
What|Removed |Added
Target Milestone|--- |12.0
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100164
--- Comment #18 from David Edelsohn ---
Because the _M_try_acquire patch was not yet committed to trunk when I tested
and bootstrap on trunk now is broken due to other, unrelated patches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100186
--- Comment #2 from David Edelsohn ---
Created attachment 50650
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50650&action=edit
pre-processed source for lto-wrapper.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100186
--- Comment #5 from David Edelsohn ---
For example, in GCC 6:
#if defined(_GLIBCXX_HAS_GTHREADS) && defined(_GLIBCXX_USE_C99_STDINT_TR1)
namespace std _GLIBCXX_VISIBILITY(default)
{
_GLIBCXX_BEGIN_NAMESPACE_VERSION
/**
* @defgroup thread
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97522
David Edelsohn changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97522
--- Comment #2 from David Edelsohn ---
fixed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98139
--- Comment #2 from David Edelsohn ---
I bootstrap GCC on AIX with, and the instructions in the CompileFarm wiki
recommend, --disable-werror.
If that currently is the only problem, we're lucky. I don't know that this
hack is better. Shrug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98139
--- Comment #5 from David Edelsohn ---
It has nothing to do with the proper way to install GCC on AIX.
It was not the only -Werror failure on AIX. That is why I said, if that's the
only problem, we're lucky. The -Werror failures change.
The p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98139
David Edelsohn changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98225
David Edelsohn changed:
What|Removed |Added
CC||dje at gcc dot gnu.org
Stat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98225
--- Comment #18 from David Edelsohn ---
PASS: outputs exe savetmp namedb: outputs-outputs-0.i
PASS: outputs exe savetmp namedb: outputs-outputs-0.s
PASS: outputs exe savetmp namedb: outputs-outputs-0.o
PASS: outputs exe savetmp namedb: outputs.ar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98613
David Edelsohn changed:
What|Removed |Added
Ever confirmed|0 |1
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98613
Bug ID: 98613
Summary: vstring mov testsuite failures on AIX
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98613
--- Comment #2 from David Edelsohn ---
These failures appeared with Martin Sebor's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98613
David Edelsohn changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98613
David Edelsohn changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90859
David Edelsohn changed:
What|Removed |Added
CC||dje at gcc dot gnu.org
--- Comment #7 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98799
Bug ID: 98799
Summary: [10 Regression] vector_set_var ICE
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98799
David Edelsohn changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98799
--- Comment #2 from David Edelsohn ---
As with vector_extract, the P8 version requires TARGET_DIRECT_MOVE_64BIT.
I think that this needs something like the following:
--- rs6000.c2021-01-22 11:45:39.0 -0500
+++ cc.c2021-01-2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98799
--- Comment #3 from David Edelsohn ---
Created attachment 50042
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50042&action=edit
patch
This is a version of the patch that compiles. I moved the definitions of
vector_set_var after the p8 an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98799
David Edelsohn changed:
What|Removed |Added
Attachment #50042|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98926
David Edelsohn changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98979
David Edelsohn changed:
What|Removed |Added
Target|powerpc64*-linux-gnu, |powerpc64*-linux-gnu,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99094
Bug ID: 99094
Summary: [AIX] Thread local uninitialized data allocated in
.comm
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priori
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99094
David Edelsohn changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98979
--- Comment #11 from David Edelsohn ---
The failures have been resolved on AIX.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98384
--- Comment #21 from David Edelsohn ---
It similarly continues to fail on AIX:
long_double.cc:192: void test02(): Assertion '!memcmp(printf_buffer,
to_chars_buffer, output_length)' failed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94177
David Edelsohn changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89096
David Edelsohn changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95549
David Edelsohn changed:
What|Removed |Added
CC||dje at gcc dot gnu.org
--- Comment #3 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98171
--- Comment #1 from David Edelsohn ---
gcc119 should be functioning again.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100805
Bug ID: 100805
Summary: __int128 should be disabled for non-extended -std=
options
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101020
David Edelsohn changed:
What|Removed |Added
Last reconfirmed||2021-06-11
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101166
Bug ID: 101166
Summary: Add SPDX license identifiers
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: other
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108734
David Edelsohn changed:
What|Removed |Added
CC||dje at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108315
--- Comment #12 from David Edelsohn ---
We're working to add a Power10 system to the Compile Farm. The systems are at
OSUOSL, but Power10 doesn't have official KVM support so the interface to the
OpenStack management system is complicated.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103784
--- Comment #11 from David Edelsohn ---
Have you looked on the GCC mailing list for zero-extend elimination (zee) and
sign-extend elimination (see)? The many, previous proposals for such passes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26374
--- Comment #20 from David Edelsohn ---
Double-double has advantages and disadvantages. You're welcome to debate
William Kahan about the choice instead of making snarky comments here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106637
David Edelsohn changed:
What|Removed |Added
Last reconfirmed||2022-08-16
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106855
Bug ID: 106855
Summary: [13 Regression] Removal of stabs/xcoff debugging broke
bootstrap on AIX
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: nor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106855
David Edelsohn changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106855
--- Comment #2 from David Edelsohn ---
dwarf2out.cc uses XCOFF_DEBUGGING_INFO to emit DWARF information with XCOFF
syntax.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107018
Bug ID: 107018
Summary: [13 Regression] libgcc unwind-dw2-fde references
undeclared variable
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107221
Bug ID: 107221
Summary: [13 Regression] libstdc++ EH no matching function
__gnu_cxx::__scoped_lock::__scoped_lock
Product: gcc
Version: unknown
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107221
David Edelsohn changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107239
Bug ID: 107239
Summary: Coroutine code generation bug
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: C++-Coroutine, wrong-code
Severity: normal
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107239
--- Comment #1 from David Edelsohn ---
https://twitter.com/novacisko/status/1580056176040980481
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57955
--- Comment #26 from David Edelsohn ---
As Bill mentioned, one can increase the alignment of a large constant, but
there is no way for the hooks that set alignment to recognize that the constant
will be assigned to variable with stricter alignmen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104101
Bug ID: 104101
Summary: [12 Regression] libstdc++ shared_ptr_atomic fails on
AIX
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104123
Bug ID: 104123
Summary: 29_atomics/headers/stdatomic.h/c_compat.cc fails on
AIX
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102519
David Edelsohn changed:
What|Removed |Added
Resolution|--- |FIXED
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103004
David Edelsohn changed:
What|Removed |Added
CC||dje at gcc dot gnu.org
Ever confir
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103759
Bug ID: 103759
Summary: [12 Regression] memcpy-chk failure for 32 bits
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103759
David Edelsohn changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103759
David Edelsohn changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102068
David Edelsohn changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99557
David Edelsohn changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102147
Bug ID: 102147
Summary: IRA dependent on 32-bit vs 64-bit register size
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102147
David Edelsohn changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102147
--- Comment #2 from David Edelsohn ---
Created attachment 51389
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51389&action=edit
Pre-processed subset of tree-vect-slp.c
$ gcc -O2 -fno-exceptions
produces different conflicts and register
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102147
--- Comment #5 from David Edelsohn ---
Vlad privately commented: "I suspect order of processing conflicts might depend
on their representation."
The two representations may produce different results and the heuristics to
choose the representati
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102148
David Edelsohn changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102349
--- Comment #1 from David Edelsohn ---
I can't duplicate this failure in a native build. And rs6000.c:21750 doesn't
correspond to any statement. Can you provide some additional information or
source code context?
rs6000_xcoff_encode_section_i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102349
--- Comment #7 from David Edelsohn ---
As we discussed on IRC
symtab_node::exists (decl) && symtab_node::get (decl)->alias
seems better because that function does not need to create the summary for its
internal use. The function should not en
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102349
--- Comment #8 from David Edelsohn ---
This needs an additional adjustment. The encoding decoration needs to be
applied if the decl isn't an alias. That means both a null summary *OR* the
decl is not explicitly an alias.
I'm proposing the fol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102519
Bug ID: 102519
Summary: [12 Regression] VRP Jump threader memory explosion
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: memory-hog
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102519
David Edelsohn changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102519
--- Comment #7 from David Edelsohn ---
Have you tried a native PPC64LE Linux build?
AIX defaults to 32 bit, and it's big endian. I wouldn't expect that to affect
the memory usage, but I'm mentioning it.
Did you try to compiler gcc/testsuite/gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102527
David Edelsohn changed:
What|Removed |Added
CC||dje at gcc dot gnu.org
Ever confir
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102519
--- Comment #11 from David Edelsohn ---
tree VRP threader : 0.25 ( 2%) 0.03 ( 1%) 0.76 ( 1%)
7804k ( 2%)
Despite that report output, prior to the two patches ending with
ef1e524fd87a679f5da06116029c66a84daac80 "Remov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102519
--- Comment #12 from David Edelsohn ---
GCC non-quiet mode shows:
...
g_31_31_16 f_31_31_17 g_31_31_17 f_31_31_23 g_31_31_23 f_31_31_24 g_31_31_24
f_31_31_25 g_31_31_25 f_31_31_29 g_31_31_29 f_31_31_30 g_31_31_30 f_31_31_31
g_31_31_31
Analyzing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102519
--- Comment #14 from David Edelsohn ---
I tried the patch, but, unfortunately, it exceeds the memory limit in the same
manner.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102519
--- Comment #15 from David Edelsohn ---
I annotated execute_vrp_threader() to call getrusage() and print the size of
RSS around each call to threader.thread_jumps(). It consistently is growing,
but not in the threader itself. Was the former VP
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102519
--- Comment #18 from David Edelsohn ---
Yea! That fixes the *worst* of the memory growth problem for me.
It still is growing, but much more slowly. RSS now grows from 569788 to 642076
for the final function, instead of 783896 before it died o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102344
David Edelsohn changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102339
David Edelsohn changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102323
David Edelsohn changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
1 - 100 of 155 matches
Mail list logo
