[Bug fortran/104131] ICE in gfc_conv_array_ref, at fortran/trans-array.c:3810
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104131 --- Comment #8 from Tobias Burnus --- (In reply to anlauf from comment #7) > (In reply to Tobias Burnus from comment #6) > > !$omp task detach (x) > > !$omp end task > > > > This seems to be valid. OpenMP mostly only rejects coindexed variables like: > > Alright, I did not expect this, and no other compiler I have access to > accepts it. On the technical side, a coarray is just a normal variable that is also remotely accessible; I think it is usually just 'malloc'ed but in principle the coarray library could allocate it also in special memory. There might be some issues when used inside target regions, i.e. on a device with shared memory (page migrations etc.) but, otherwise, there is no real reason to disallow it. Of course, everything related to memory allocation or coindexed access will not work (in general - at least some special cases will fail). * * * In terms of the OpenMP specification, there is a section "Normative References"; * in OpenMP 5.0, it has: "Fortran 2008 ... their use may result in unspecified behavior ... Coarrays" * in OpenMP 5.1, there are no exceptions for 2008 and Fortran 2018 with a new list of unspecified behavior was added. Thus, coarrays were never explicitly rejected but in 5.0 their use might result in unspecified behavior, i.e. an implementation could reject it. Since 5.1, they can be used where deemed to be okay. (Disclaimer: What might be okay for most implementation can be unimplementable in another; additionally, some corner cases might have been overlooked which do cause problems.) * * * My quotes in comment 6 were from OpenMP 5.2, the latest release. TR11 (pre-6.0) is the latest spec, semi-solid but breaking changes are permitted until the final 6.0 (to fix oversights).
[Bug c++/111897] Initialization of _Float16 with f.p. constant gives false warning
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111897
--- Comment #3 from Agner Fog ---
I have asked the authors of the linked document. They say that the example in
the document is wrong. The latest version still has the error in the example:
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p1467r9.html
The compiler should give warnings for all of these:
_Float16 A = 1.5;
_Float16 B(1.5);
_Float16 C{1.5};
but no warning for integers:
_Float16 D = 2;
It is fine to give a warning rather than an error message when the intention is
obvious and there is no ambiguity.
Below is my conversation with David Olsen:
That’s correct. Conversions between integral and floating-point types are
standard conversions, in both directions, which means they are implicit
conversions. That was covered by preexisting wording in the standard, so P1467
doesn’t talk about those conversions. There isn’t a good way for the standard
to clearly specify which conversions are lossless and which are potentially
lossy, so we didn’t try to limit int/float conversions involving extended
floating-point types to just the safe conversions.
From: Agner Fog
Sent: Tuesday, October 24, 2023 10:26 PM
To: David Olsen ; gri...@griwes.info
Subject: Re: Problem with P1467R4 C++ std. proposal
Thank you for a clear answer.
I don't see any mentioning of implicit conversion from integer to extended
floating point types. Is that allowed?
gcc 13.1 gives no warning for implicit conversion from integer to float16:
_Float16 A = 3; // no warning
_Float16 A = 3.; // warning
Is that correct?
- Agner
On 24/10/2023 19.29, David Olsen wrote:
The final version of P1467 is R9,
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p1467r9.html . The
GCC 13 release notes contain a link to that version. Where do you see the link
to R4?
The issue of initialization of extended floating-point type variables was
raised and discussed during the standardization process. R9 contains a long
discussion of the issue, with some of the ways that we tried to fix the problem
of initialization.
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p1467r9.html#implicit-constant
After some back and forth, the consensus was to leave the implicit conversion
rules unchanged for initialization, because the potential solutions have their
own problems. So all of
_Float16 A = 1.5;
_Float16 B(1.5);
_Float16 C{1.5};
are ill-formed and should result in a compiler diagnostic. I am pleased
that GCC reports only a warning and not a hard error, since the user's intent
is obvious.
Yes, the example in section 5.6.1 is wrong. The mistake is still there in
R9 of the paper. It should be
float f32 = 1.0f;
std::float16_t f16 = 2.0f16;
std::bfloat16_t b16 = 3.0bf16;
On the more general issue of how much the new extended floating-point types
should behave like the existing standard floating-point types, there was a long
and useful discussion about this topic at a committee meeting in Feb 2020.
There is general agreement that many of the defaults in C++ are wrong and can
make it easier to write badly behaving code. Whenever new features are added,
there is tension between the consistency of having them behave like existing
features and the safety of choosing different defaults that makes it easier to
write correct code. These competing goals and the consequences and tradeoffs
of both of them were explicitly laid out and discussed at the Feb 2020 meeting,
and at the end of the discussion there was strong consensus (though not
unanimity) to go with safety over consistency for implicit conversions of
extended floating-point types.
int16_t is in the std namespace in C++. For C compatibility it is also
available at global scope if you include (defined by the C standard)
instead of (defined by the C++ standard). The C++ standard doesn't
define any names at global scope other than 'operator new' and 'operator
delete'. Defining float16_t to be a global scope would have been a huge
departure from existing practice.
-Original Message-
From: Agner Fog
Sent: Tuesday, October 24, 2023 8:03 AM
To: David Olsen ; gri...@griwes.info
Subject: Problem with P1467R4 C++ std. proposal
Dear David Olsen and Michał Dominiak
I don't know who to contact regarding C++ standard development, so I am
taking the liberty to contact you as the authors of P1467R4,
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p1467r4.html#implicit
It is unclear whether the rules for implicit conversion relate to
initialization and assignment.
gcc version 13.1 gives warnings for the following cases with reference to
the above document:
_Float16 A = 1.5;
_Float16 B(1.5);
_Float16 C{1.5};
The last one should probably not have a warning, the other ones are
unclear. Initialization with an integer constant gives no warning message.
The example in
[Bug testsuite/111969] RISC-V rv32gcv: 12 grouped flaky failures
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111969 --- Comment #2 from Andreas Schwab --- They never fail on real hardware (hifive unleashed).
[Bug tree-optimization/111970] [14 regression] SLP for non-IFN gathers result in RISC-V test failure on gather since r14-4745-gbeab5b95c58145
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111970 --- Comment #3 from Li Pan --- Double confirmed the trunk of GCC still has this issue.
[Bug middle-end/111972] New: [14 regression] missed vectorzation for bool a = j != 1; j = (long int)a;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111972
Bug ID: 111972
Summary: [14 regression] missed vectorzation for bool a = j !=
1; j = (long int)a;
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: crazylht at gmail dot com
Target Milestone: ---
cat test.c
double
foo() {
long n3 = 345, xtra = 7270;
long i,ix;
long j;
double Check;
/* Section 3, Conditional jumps */
j = 0;
{
for (ix=0; ix2)j = 0;
else j = 1;
if(j<1)j = 1;
else j = 0;
}
}
}
Check = Check + (double)j;
return Check;
}
The different between gcc 13 dump and gcc14 dump is
GCC13 we have
[local count: 1063004411]:
# i_16 = PHI
# j_18 = PHI <_7(8), j_21(5)>
# ivtmp_15 = PHI
_7 = j_18 ^ 1;
i_13 = i_16 + 1;
ivtmp_6 = ivtmp_15 - 1;
if (ivtmp_6 != 0)
goto ; [99.00%]
else
goto ; [1.00%]
GCC14 we have
[local count: 1063004410]:
# i_17 = PHI
# j_19 = PHI <_14(8), j_22(5)>
# ivtmp_16 = PHI
_9 = j_19 != 1;
_14 = (long int) _9;
i_13 = i_17 + 1;
ivtmp_15 = ivtmp_16 - 1;
if (ivtmp_15 != 0)
goto ; [98.99%]
else
goto ; [1.01%]
Vectorizer can handle
_7 = j_18 ^ 1;
but not
_9 = j_19 != 1;
_14 = (long int) _9;
../test.C:11:18: note: vect_is_simple_use: operand j_19 != 1, type of def:
internal
../test.C:11:18: note: mark relevant 2, live 0: _9 = j_19 != 1;
../test.C:11:18: note: worklist: examine stmt: _9 = j_19 != 1;
../test.C:11:18: note: vect_is_simple_use: operand j_19 = PHI <_14(8),
j_22(5)>, type of def: unknown
../test.C:11:18: missed: Unsupported pattern.
../test.C:15:6: missed: not vectorized: unsupported use in stmt.
../test.C:11:18: missed: unexpected pattern.
The difference comes from phiopt2.
[Bug analyzer/111213] -Wanalyzer-out-of-bounds false negative with `return arr[9];` at -O1 and above
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111213 --- Comment #3 from mengli ming --- (In reply to David Malcolm from comment #1) > (In reply to mengli ming from comment #0) > > Thanks for filing this bug. > > > Hi, this case (https://godbolt.org/z/98PMz1KKz) contains an out-of-bound > > error (stmt: `return arr[9];`). At -O0, the analyzer can report this > > warning. However, at -O1, -O2, and -O3, the analyzer doesn't report that. > > This is a side-effect of how late the analyzer runs. Adding > -fdump-ipa-analyzer=stdder > shows that at -O1 and above, the "arr[9]" access is optimized away before > the analyzer "sees" it. > > See e.g.: > https://godbolt.org/z/YjffsMYW4 > > My hypothesis is that the optimizer sees the undefined behavior and > optimizes the function away (but I haven't looked into the details). > > If that's the case, that's a strong argument that the analyzer should run > earlier. I'm not sure if we have an existing bug about that. Many thanks!!!
[Bug analyzer/110520] -Wanalyzer-null-dereference false nagetive with `*ptr = 10086`
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110520 --- Comment #2 from mengli ming --- (In reply to David Malcolm from comment #1) > Thanks for filing this bug. > > With trunk (for gcc 14) I correctly get a NPD warning (true positive): > https://godbolt.org/z/a5h38cz7d > > With gcc 13.2, I don't (false negative): > https://godbolt.org/z/PKnToYK8v > > I've been rewriting C string handling for gcc 14, so it's likely this now > working is a side-effect of that. > > Keeping open to track adding a regression test for this. Thank you for your explanation. (^_^)
[Bug analyzer/111095] -Wanalyzer-out-of-bounds false negative with `return l_1322[9];` at -O1 and above
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111095 --- Comment #3 from mengli ming --- (In reply to David Malcolm from comment #1) > Thanks for filing this bug. > > This looks similar to bug 111213. > > Adding -fdump-ipa-analyzer=stderr shows that at -O1 and above, the entire > body of the function is optimized away before the analyzer even sees it > (presumably due to undefined behavior). > > My hypothesis is that the optimizer sees the undefined behavior and > optimizes the function away (but I haven't checked the details). > > If that's the case, that's a strong argument that the analyzer should run > earlier. I'll open a bug about that. Thank you for the detailed explanation, David. I appreciate it.
[Bug target/111772] ICE on gfortran.dg/transpose_conjg_1.f90 in regrename.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111772 Filip Kastl changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Filip Kastl --- Ran on my machine again. Confirmed that the bug no longer occurs. Marking as fixed.
[Bug target/111973] New: [RISC-V] attribute interrupt yields unaligned stack access
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111973
Bug ID: 111973
Summary: [RISC-V] attribute interrupt yields unaligned stack
access
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jonathan.jonsson at gaisler dot com
Target Milestone: ---
Created attachment 56201
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56201&action=edit
cpp code to reproduce the issue
When adding the interrupt attribute to a function such as this:
void vstvec_ssi() __attribute__((interrupt("supervisor")));
The code generated for the interrupt attribute is corrupted by an unintended
unaligned access. I didn't have this issue in gcc-13. The generated assembly
first saves some of the float registers and then when the integer registers are
about to be saved the offset for the stack pointer gets unaligned. This does
not occur when I don't call external functions.
In relation to all of this, a question I have is if it is possible to tell GCC
to not generate code to save float and vector registers on an interrupt?
4c: 08f13027fsd fa5,128(sp) //Aligned
50: 07013c27fsd fa6,120(sp) //Aligned
54: 16512e23sw t0,380(sp) //Aligned
58: 16613a23sd t1,372(sp) //No longer aligned
5c: 16713623sd t2,364(sp)
Command line:
riscv64-unknown-elf-g++ -mcmodel=medany -static -std=gnu++20 -fno-common
-fno-builtin march=rv64gvh_zba_zbb_zbc_zbs_zfh_zbkb_zicsr_zifencei_zicbom -O3
-ggdb -mabi=lp64 -Wcast-align -Wstack-usage=960KB -Wsign-compare
-Wmaybe-uninitialized -Wuninitialized -Wno-comment -save-temps -c -o
gcc_bug_reproduce.o gcc_bug_reproduce.cpp
GCC version:
Using built-in specs.
COLLECT_GCC=riscv64-unknown-elf-g++
COLLECT_LTO_WRAPPER=/gsl/tools/riscv-gnu-toolchain/bin/../lib/gcc/riscv64-unknown-elf/14.0.0/lto-wrapper
Target: riscv64-unknown-elf
Configured with:
/tmp/riscv-gnu-toolchain-temp/riscv-gnu-toolchain/gcc/configure
--target=riscv64-unknown-elf --prefix=/tmp/riscv-gnu-toolchain --disable-shared
--disable-threads --enable-languages=c,c++ --with-pkgversion=g0fc13e8c0e3
--with-system-zlib --enable-tls --with-newlib
--with-sysroot=/tmp/riscv-gnu-toolchain/riscv64-unknown-elf
--with-native-system-header-dir=/include --disable-libmudflap --disable-libssp
--disable-libquadmath --disable-libgomp --disable-nls
--disable-tm-clone-registry --src=.././gcc --enable-multilib --with-abi=lp64d
--with-arch=rv64imafdc --with-tune=rocket --with-isa-spec=20191213
'CFLAGS_FOR_TARGET=-Os-mcmodel=medlow' 'CXXFLAGS_FOR_TARGET=-Os
-mcmodel=medlow'
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20231024 (experimental) (g0fc13e8c0e3)
[Bug analyzer/111441] internal compiler error: in fold_binary_loc, at fold-const.cc:11580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441 --- Comment #4 from mengli ming --- Hi, I've checked recently and the crash still persists, even with the -O0 optimization level.
[Bug rtl-optimization/111971] ICE: maximum number of generated reload insns per insn achieved (90)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111971 --- Comment #5 from Jiu Fu Guo --- With a bisect, the result shows "85419ac59724b7ce710ebb4acf03dbd747edeea3 is the first bad commit".
[Bug analyzer/111095] -Wanalyzer-out-of-bounds false negative with `return l_1322[9];` at -O1 and above
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111095 --- Comment #4 from mengli ming --- (In reply to David Malcolm from comment #1) > Thanks for filing this bug. > > This looks similar to bug 111213. > > Adding -fdump-ipa-analyzer=stderr shows that at -O1 and above, the entire > body of the function is optimized away before the analyzer even sees it > (presumably due to undefined behavior). > > My hypothesis is that the optimizer sees the undefined behavior and > optimizes the function away (but I haven't checked the details). > > If that's the case, that's a strong argument that the analyzer should run > earlier. I'll open a bug about that. Hi David, Under the -O0 optimization level, I found another issue with this case. After commenting out irrelevant code like `for (int i = 0; i < 1; i++) ;` or `union a h;`, the analyzer reports an out-of-bound warning. Moreover, changing `*g = 0;` to `*g = 1;` also triggers the out-of-bound warning. It's puzzling.
[Bug analyzer/111095] -Wanalyzer-out-of-bounds false negative with `return l_1322[9];` at -O1 and above
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111095 --- Comment #5 from mengli ming --- Created attachment 56202 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56202&action=edit Under the `-O0` optimization level, irrelevant code affects whether the analyzer will report an out-of-bound warning.
[Bug c++/111974] New: internal error: Segmentation fault on Ubuntu 23.10 (x86-64)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111974 Bug ID: 111974 Summary: internal error: Segmentation fault on Ubuntu 23.10 (x86-64) Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: basile at starynkevitch dot net Target Milestone: --- I uploaded to refpersys.org/refpersys-gcc13bug-snapshot-25oct2023-git041d5d70aefd0.tar.bz2 a compressed tarball (29246912 bytes) of md5sum 6b1d2985ce86bd1718d05af3d93a84f9 RefPerSys is a GPLv3+ open source project for an inference engine. See http://refpersys.org/ for details. The code repository of RefPerSys is on gihtub. See the commit https://github.com/RefPerSys/RefPerSys/commit/041d5d70aefd047de4eb456432853beefffb4120 On Ubuntu 23.10 (x86-64 desktop with AMD Ryzen Threadripper 2970WX) this tarball is crashing the GCC 13.2 compiler with a reproducible GCC compiler bug. To reproduce, (using GNU make 4.3) run make cmdrepl_rps.o which crashes with rimski.x86_64 ~/RefPerSys 11:17 .0 % make cmdrepl_rps.o /usr/bin/time --append --format='%C : %S sys, %U user, %E elapsed; %M RSS' --output=_build.time g++-13 -std=gnu++17 -O1 -g3 -fPIC -Wall -Wextra -I. -I/usr/local/include -I/usr/include -I/usr/include/jsoncpp -I/usr/include/jsoncpp -I/usr/include/jsoncpp -I/usr/include/x86_64-linux-gnu -I/usr/local/include/ -DRPS_ARCH=\"x86_64\" -DRPS_HAVE_ARCH_x86_64 -DRPS_OPERSYS=\"GNU_Linux\" -DRPS_HAVE_OPERSYS_GNU_Linux -DRPS_GITID=\"041d5d70aefd047de4eb456432853beefffb4120+\" -DRPS_SHORTGITID=\"041d5d70aefd+\" -I/usr/src/Libs/lightning/include/lightning -std=gnu++17-c -o cmdrepl_rps.o cmdrepl_rps.cc cmdrepl_rps.cc:51:2: warning: #warning should declare rps_full_evaluate_repl_instance [-Wcpp] 51 | #warning should declare rps_full_evaluate_repl_instance | ^~~ cmdrepl_rps.cc:146:2: warning: #warning rps_full_evaluate_repl_expr should check that envob is an environment, with bindings and optional parent env [-Wcpp] 146 | #warning rps_full_evaluate_repl_expr should check that envob is an environment, with bindings and optional parent env | ^~~ cmdrepl_rps.cc:180:2: warning: #warning TODO: should probably define and call a rps_full_evaluate_repl_instance [-Wcpp] 180 | #warning TODO: should probably define and call a rps_full_evaluate_repl_instance | ^~~ cmdrepl_rps.cc:303:2: warning: #warning TODO: fixme evaluation of various repl_expression-s e.g. conditional, arithmetic, application [-Wcpp] 303 | #warning TODO: fixme evaluation of various repl_expression-s e.g. conditional, arithmetic, application | ^~~ cmdrepl_rps.cc:344:2: warning: #warning unimplemented rps_full_evaluate_repl_composite_object [-Wcpp] 344 | #warning unimplemented rps_full_evaluate_repl_composite_object | ^~~ cmdrepl_rps.cc:771:2: warning: #warning unimplemented Rps_CallFrame::interpret_repl_statement [-Wcpp] 771 | #warning unimplemented Rps_CallFrame::interpret_repl_statement | ^~~ cmdrepl_rps.cc:930:2: warning: #warning rpsapply_61pgHb5KRq600RLnKD should use wordexp(3) on the string [-Wcpp] 930 | #warning rpsapply_61pgHb5KRq600RLnKD should use wordexp(3) on the string | ^~~ cmdrepl_rps.cc:939:2: warning: #warning incomplete rpsapply_61pgHb5KRq600RLnKD for REPL command dump [-Wcpp] 939 | #warning incomplete rpsapply_61pgHb5KRq600RLnKD for REPL command dump | ^~~ cmdrepl_rps.cc:1050:2: warning: #warning we probably want to display some common payloads here [-Wcpp] 1050 | #warning we probably want to display some common payloads here | ^~~ cmdrepl_rps.cc:1115:2: warning: #warning REPL command show may need some local Rps_TokenSource [-Wcpp] 1115 | #warning REPL command show may need some local Rps_TokenSource | ^~~ cmdrepl_rps.cc:1206:2: warning: #warning this code should be moved into rps_show_object_for_repl above [-Wcpp] 1206 | #warning this code should be moved into rps_show_object_for_repl above | ^~~ cmdrepl_rps.cc:1212:2: warning: #warning incomplete rpsapply_7WsQyJK6lty02uz5KT should define and call rps_show_instance_for_repl [-Wcpp] 1212 | #warning incomplete rpsapply_7WsQyJK6lty02uz5KT should define and call rps_show_instance_for_repl | ^~~ cmdrepl_rps.cc:1220:2: warning: #warning incomplete rpsapply_7WsQyJK6lty02uz5KT for REPL command show [-Wcpp] 1220 | #warning incomplete rpsapply_7WsQyJK6lty02uz5KT for REPL command show | ^~~ cmdrepl_rps.cc:1262:2: warning: #warning incomplete rpsapply_2TZNwgyOdVd001uasl for REPL command help [-Wcpp] 1262 | #warning incomplete rpsapply_2TZNwgyOdVd001uasl for REPL command help | ^~~ cmdrepl_rps.cc:1298:2: warning: #warning incomplete rpsapply_28DGtmXCyOX02AuPLd for REPL command put [-Wcpp] 1298 | #warning incomplete rpsapply_28DGtmXCyOX02AuPLd for REPL comma
[Bug tree-optimization/111972] [14 regression] missed vectorzation for bool a = j != 1; j = (long int)a;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111972 Hongtao.liu changed: What|Removed |Added CC||pinskia at gcc dot gnu.org Component|middle-end |tree-optimization --- Comment #1 from Hongtao.liu --- The phiopt change is caused by r14-338-g1dd154f6407658d46faa4d21bfec04fc2551506a
[Bug c++/111897] Initialization of _Float16 with f.p. constant gives false warning
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111897 Jonathan Wakely changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #4 from Jonathan Wakely --- So closing as not-a-bug.
Bug C++ 111974 (Segmentation fault of GCC, ubuntu 23.10, compiling RefPerSys 041d5d70aefd)
Hello all, Sorry for this non-minimal bug report. I was unable to make a shorter or minimal bug example. RefPerSys is a GPLv3+ open source project for an inference engine. See http://refpersys.org/ for ambitions and some details. (I am currently more interested in working on RefPerSys than on debugging GCC, to which I did contribute earlier). RefPerSys is itself on github in https://github.com/RefPerSys/RefPerSys/ I am compiling RefPerSys (mostly C++ code, including some self generated, which is including in the below snapshot) on Ubuntu 23.10 whose g++ has version (Ubuntu 13.2.0-4ubuntu3) 13.2.0 on a desktop with AMD Ryzen Threadripper 2970WX The RefPerSys commit is https://github.com/RefPerSys/RefPerSys/commit/041d5d70aefd047de4eb456432853beefffb4120 and has a few tests: eg make test00 test01 did work a few days ago. I uploaded to http://refpersys.org/refpersys-gcc13bug-snapshot-25oct2023-git041d5d70aefd0.tar.bz2 a bzip2 compressed tarball (29246912 bytes) of md5sum 6b1d2985ce86bd1718d05af3d93a84f9 That tarball is likely to be removed in a few months. The disk space for the RefPerSys source code (with object files) take less than 200 Mbytes. To reproduce the GCC bug, run make (GNU make 4.3 from Ubuntu) in the tarball If you did reproduce it, please email me (Basile Starynkevitch, in France) to bas...@starynkevitch.net Regards -- Basile Starynkevitch (only mine opinions / les opinions sont miennes uniquement) 92340 Bourg-la-Reine, France web page: starynkevitch.net/Basile/
[Bug middle-end/111975] New: gimple front end can't round-trip vectorized code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111975
Bug ID: 111975
Summary: gimple front end can't round-trip vectorized code
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: acoplan at gcc dot gnu.org
Target Milestone: ---
Take the following testcase on aarch64:
void foo(int *restrict a, int *restrict b, int *restrict c)
{
for (int i = 0; i < 256; i++)
a[i] = b[i] + c[i];
}
compiled with -O2 -fdump-tree-optimized-gimple, we get the IR:
void __GIMPLE (ssa,guessed_local(10737416))
foo (int * restrict a, int * restrict b, int * restrict c)
{
sizetype ivtmp.17;
vector(4) int vect__8.10;
vector(4) int vect__6.9;
vector(4) int vect__4.6;
__BB(2,guessed_local(10737416)):
goto __BB3(precise(134217728));
__BB(3,loop_header(1),guessed_local(687194626)):
ivtmp.17_23 = __PHI (__BB3: ivtmp.17_19, __BB2: 0ul);
vect__4.6_9 = MEM [(int *)b_12(D) + ivtmp.17_23 * 1];
vect__6.9_27 = MEM [(int *)c_13(D) + ivtmp.17_23 * 1];
vect__8.10_28 = vect__4.6_9 + vect__6.9_27;
MEM [(int *)a_14(D) + ivtmp.17_23 * 1] = vect__8.10_28;
ivtmp.17_19 = ivtmp.17_23 + 16ul;
if (ivtmp.17_19 != 1024ul)
goto __BB3(guessed(132120577));
else
goto __BB4(guessed(2097151));
__BB(4,guessed_local(10737416)):
return;
}
but trying to compile this with -fgimple shows several problems:
- the type sizetype isn't known.
- ivtmp.17 isn't accepted as a variable name (indeed none of the variables
with . in the name are accepted).
- the type vector(4) int isn't understood by the gimple FE.
If I fix these issues by declaring the types as follows:
typedef unsigned long sizetype;
typedef int __attribute__((vector_size(16))) V;
and substituting all uses of the old type names, and also rename all variables
to replace . with _, then it is nearly accepted. One remaining problem seems to
be that the MEM syntax isn't accepted:
vect__4_6_9 = MEM [(int *)b_12(D) + ivtmp_17_23 * 1];
gives:
error: 'MEM' undeclared (first use in this function)
and attempting to convert the MEM to use something closer to the syntax in the
gcc.dg/gimplefe-* tests, this still fails:
vect__4_6_9 = __MEM ((int *)b_12(D) + ivtmp_17_23 * 1);
is rejected with:
error: expected ')' before '*' token
. It would be good if these issues could be fixed so that optimized gimple can
be round-tripped without laborious manual fixing of the input. Even with that,
it's still not clear how to make the MEM expressions here get accepted.
[Bug c++/111974] internal error: Segmentation fault on Ubuntu 23.10 (x86-64) - compiling RefPerSys
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111974 --- Comment #1 from Basile Starynkevitch --- To reproduce the GCC bug: rm -vf cmdrepl_rps.o make cmdrepl_rps.o
[Bug modula2/111955] isnan support in Builtins.def is missing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111955 --- Comment #4 from CVS Commits --- The master branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:8bb655d0c56502798d664ab0c1685bbab4aaa454 commit r14-4921-g8bb655d0c56502798d664ab0c1685bbab4aaa454 Author: Gaius Mulley Date: Wed Oct 25 11:04:12 2023 +0100 PR modula2/111955 introduce isnan support to Builtins.def This patch introduces isnan, isnanf and isnanl to Builtins.def. It requires fallback functions isnan, isnanf, isnanl to be implemented in libgm2/libm2pim/wrapc.cc and gm2-libs-ch/wrapc.c. Access to the GCC builtin isnan tree is provided by adding an isnan definition and support functions to gm2-gcc/m2builtins.cc. gcc/m2/ChangeLog: PR modula2/111955 * gm2-gcc/m2builtins.cc (gm2_isnan_node): New tree. (DoBuiltinIsnan): New function. (m2builtins_BuiltInIsnan): New function. (m2builtins_init): Initialize gm2_isnan_node. (list_of_builtins): Add define for __builtin_isnan. * gm2-libs-ch/wrapc.c (wrapc_isnan): New function. (wrapc_isnanf): New function. (wrapc_isnanl): New function. * gm2-libs/Builtins.def (isnanf): New procedure function. (isnan): New procedure function. (isnanl): New procedure function. * gm2-libs/Builtins.mod: * gm2-libs/wrapc.def (isnan): New function. (isnanf): New function. (isnanl): New function. libgm2/ChangeLog: PR modula2/111955 * libm2pim/wrapc.cc (isnan): Export new function. (isnanf): Export new function. (isnanl): Export new function. gcc/testsuite/ChangeLog: PR modula2/111955 * gm2/pimlib/run/pass/testnan.mod: New test. Signed-off-by: Gaius Mulley
[Bug modula2/111955] isnan support in Builtins.def is missing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111955 Gaius Mulley changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Gaius Mulley --- Closing now that the patch has been applied.
[Bug objc++/111920] [14 Regression] encode-{8,9,10}.mm internal compiler error: in tsubst_expr, at cp/pt.cc:21533
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111920 --- Comment #4 from Jonathan Wakely --- N.B. this same ICE was affecting C++ too, several libstdc++ tests failed with -std=c++20, e.g. GLIBCXX_TESTSUITE_STDS=20 make check RUNTESTFLAGS=conformance.exp=*/48101-2_neg.cc
[Bug c++/111974] internal error: Segmentation fault on Ubuntu 23.10 (x86-64) - compiling RefPerSys
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111974 --- Comment #2 from Jonathan Wakely --- (In reply to Basile Starynkevitch from comment #0) > Please submit a full bug report, with preprocessed source (by using > -freport-bug). ^^^
[Bug other/111976] New: Large constant zero-valued objects should go in .bss rather than .rodata
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111976
Bug ID: 111976
Summary: Large constant zero-valued objects should go in .bss
rather than .rodata
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: redbeard0531 at gmail dot com
Target Milestone: ---
Right now constant objects always go in .rodata. This is nice because it will
give a nice loud error if you ever write to it. However, .rodata takes up space
in the binary file and in memory at runtime. If you instead put it in .bss it
takes up no space in the binary file and, at least on linux, it gets backed by
a single zero-filled page of physical memory. Ideally there would be something
like .robss which gave you the best of both worlds, but this is admittedly
niche for all the effort to add a new section like that. I think the best
option is to leave it in .rodata for non-optimized builds to catch bugs, but
when optimizing, especially with -Os, put it in .bss.
Repro https://www.godbolt.org/z/3rWvTrsTv:
constexpr int GB = 1024*1024*1024;
// Goes in .bss - no space in binary or runtime.
char nonconst_zeros[GB] = {};
// Goes in .rodata - expensive in binary size and runtime memory.
extern const char const_zeros[GB]; // force usage
const char const_zeros[GB] = {};
.globl const_zeros
.section.rodata
.align 32
.type const_zeros, @object
.size const_zeros, 1073741824
const_zeros:
.zero 1073741824
.globl nonconst_zeros
.bss
.align 32
.type nonconst_zeros, @object
.size nonconst_zeros, 1073741824
nonconst_zeros:
.zero 1073741824
[Bug libstdc++/111936] std::stacktrace cannot be used in a shared library
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111936 --- Comment #11 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:f32c1e1e96ffef6512ce025942b51f3967a3e7f2 commit r14-4922-gf32c1e1e96ffef6512ce025942b51f3967a3e7f2 Author: Jonathan Wakely Date: Tue Oct 24 16:56:30 2023 +0100 libstdc++: Build libstdc++_libbacktrace.a as PIC [PR111936] In order for std::stacktrace to be used in a shared library, the libbacktrace symbols need to be built with -fPIC. Add the libtool -prefer-pic flag to the commands in src/libbacktrace/Makefile so that the archive contains PIC objects. libstdc++-v3/ChangeLog: PR libstdc++/111936 * src/libbacktrace/Makefile.am: Add -prefer-pic to libtool compile commands. * src/libbacktrace/Makefile.in: Regenerate.
[Bug other/111976] Large constant zero-valued objects should go in .bss rather than .rodata
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111976 --- Comment #1 from Mathias Stearn --- Just to be clear, I think we should only do this for "large" objects or collections of objects. If you did it for small objects in general, there is a risk that they will spread out mutable data that is written to over more pages, so that you end up with more runtime anonymous pages, rather than read-only pages backed by the file cache, so they end up being more expensive. I think a good rule to prevent this would be to only do it for objects larger than a page, and possibly add page alignment to them. It may also be possible to collect enough smaller objects together to make it worth doing this. Not sure how often that occurs in practice though. Also at -Os it may make sense to do this for any size object putting since small objects in .bss will still shrink the binary size. Not sure how users of -Os would react to tradeoffs involving runtime memory consumption vs binary size.
[Bug ipa/96503] attribute alloc_size effect lost after inlining
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96503 --- Comment #5 from Siddhesh Poyarekar --- This could work for alloc_size, but not quite for access. pointer_with_size (or __builtin_with_size as you suggested in that thread) would need to express access semantics too, to be able to express everything that access does.
[Bug ipa/96503] attribute alloc_size effect lost after inlining
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96503 --- Comment #6 from Siddhesh Poyarekar --- So basically, __builtin_with_access(void *ptr, size_t size, int access) where access == -1: Unknown access semantics 0: none 1: read_only 2: write_only 3: read_write should address both access and alloc_size and even counted_by. We would need to emit the builtin in the caller as well as callee of the function that has the access attribute while for alloc_size, we only need to emit this in the caller.
[Bug c++/111974] internal error: Segmentation fault on Ubuntu 23.10 (x86-64) - compiling RefPerSys
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111974 --- Comment #3 from Basile Starynkevitch --- This bug seems to have disappeared with a trunk GCC (GCC commit f32c1e1e96ffef) compiled from its source code /usr/local/bin/g++-trunk --version g++-trunk (GCC) 14.0.0 20231025 (experimental) Copyright (C) 2023 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. where the g++ trunk code has been configured then compiled using '../gcc/configure' '--enable-host-shared' '--program-suffix=-trunk' '--enable-debug' '--disable-bootstrap' 'CFLAGS=-O2 -g' 'CXXFLAGS=-O2 -g' '--enable-languages=c,c++,jit,lto'
[Bug target/111677] [12/13/14 Regression] darktable build on aarch64 fails with unrecognizable insn due to -fstack-protector changes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111677
Alex Coplan changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
--- Comment #13 from Alex Coplan ---
The problem seems to be this code in aarch64_process_components:
while (regno != last_regno)
{
bool frame_related_p = aarch64_emit_cfi_for_reg_p (regno);
machine_mode mode = aarch64_reg_save_mode (regno);
rtx reg = gen_rtx_REG (mode, regno);
poly_int64 offset = frame.reg_offset[regno];
if (frame_pointer_needed)
offset -= frame.bytes_below_hard_fp;
rtx addr = plus_constant (Pmode, ptr_reg, offset);
rtx mem = gen_frame_mem (mode, addr);
which emits a TFmode mem with offset 512, which is out of range for TFmode (so
we later ICE with an unrecognisable insn). Presumably this just needs tweaking
to emit a new base anchor in the case of large offsets like this. It looks
like the code in aarch64_save_callee_saves already does this.
[Bug d/111977] New: test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111977 Bug ID: 111977 Summary: test Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56203 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56203&action=edit test
[Bug d/111980] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111980 Bug ID: 111980 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56206 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56206&action=edit fsdf testtesttesttesttest
[Bug ada/111978] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111978 Bug ID: 111978 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: ada Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com CC: dkm at gcc dot gnu.org Target Milestone: --- Created attachment 56204 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56204&action=edit test
[Bug c++/111983] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111983 Bug ID: 111983 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56209 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56209&action=edit ggfgg testtesttesttesttest
[Bug d/111979] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111979 Bug ID: 111979 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56205 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56205&action=edit rrr testtesttesttesttest
[Bug bootstrap/111981] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111981 Bug ID: 111981 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56207 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56207&action=edit dsdd testtesttesttesttest
[Bug boehm-gc/111985] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111985 Bug ID: 111985 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: boehm-gc Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56211 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56211&action=edit hhg testtesttesttesttest
[Bug d/111986] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111986 Bug ID: 111986 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56212 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56212&action=edit ss testtesttesttesttest
[Bug c++/111982] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111982 Bug ID: 111982 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56208 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56208&action=edit ggffg testtesttesttesttest
[Bug bootstrap/111990] New: aaaaaaa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111990 Bug ID: 111990 Summary: aaa Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56216 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56216&action=edit uy testtesttesttesttest
[Bug c/111988] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111988 Bug ID: 111988 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56214 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56214&action=edit jhj testtesttesttesttest
[Bug c/111989] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111989 Bug ID: 111989 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56215 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56215&action=edit sfd testtesttesttesttest
[Bug c++/111987] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111987 Bug ID: 111987 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56213 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56213&action=edit testtesttesttesttest
[Bug c/111994] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111994 Bug ID: 111994 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56220 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56220&action=edit 3 testtesttesttesttest
[Bug c++/111984] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111984 Bug ID: 111984 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56210 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56210&action=edit ffddf testtesttesttesttest
[Bug bootstrap/111992] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111992 Bug ID: 111992 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56218 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56218&action=edit 5 testtesttesttesttest
[Bug c/111991] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111991 Bug ID: 111991 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56217 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56217&action=edit aa testtesttesttesttest
[Bug c++/111996] New: testtesttesttesttesttesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111996 Bug ID: 111996 Summary: testtesttesttesttesttesttesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56222 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56222&action=edit aaa testtesttesttesttesttest
[Bug d/111993] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111993 Bug ID: 111993 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56219 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56219&action=edit a testtesttesttesttest
[Bug c++/111995] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111995 Bug ID: 111995 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56221 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56221&action=edit 2 testtesttesttesttest
[Bug c++/111997] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111997 Bug ID: 111997 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56223 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56223&action=edit aaa testtesttesttesttest
[Bug d/111998] New: atesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111998 Bug ID: 111998 Summary: atesttesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56224 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56224&action=edit aa testtesttesttesttest
[Bug d/111999] New: testtesttesttesttesttesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111999 Bug ID: 111999 Summary: testtesttesttesttesttesttesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56225 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56225&action=edit aaa testtesttesttesttest
[Bug c/112000] New: testtesttesttesttesttesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112000 Bug ID: 112000 Summary: testtesttesttesttesttesttesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56226 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56226&action=edit testtesttesttesttesttesttesttesttesttest
[Bug bootstrap/112001] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112001 Bug ID: 112001 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56227 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56227&action=edit testtesttesttesttest
[Bug c++/112002] New: testtesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112002 Bug ID: 112002 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56228 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56228&action=edit uu testtesttesttesttest
[Bug c/112003] New: atesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112003 Bug ID: 112003 Summary: atesttesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56229 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56229&action=edit a testtesttesttesttest
[Bug bootstrap/112004] New: aztesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112004 Bug ID: 112004 Summary: aztesttesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56230 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56230&action=edit a testtesttesttesttest
[Bug bootstrap/112005] New: testtesttesttesttesttesttesttesttesttestd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112005 Bug ID: 112005 Summary: testtesttesttesttesttesttesttesttesttestd Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56231 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56231&action=edit a testtesttesttesttest
[Bug bootstrap/112006] New: eeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112006 Bug ID: 112006 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56232 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56232&action=edit aaa testtesttesttesttest
[Bug d/112007] New: eeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112007 Bug ID: 112007 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56233 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56233&action=edit a testtesttesttesttest
[Bug bootstrap/112008] New: eeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112008 Bug ID: 112008 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56234 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56234&action=edit a testtesttesttesttest
[Bug bootstrap/112009] New: eeeetesttesttesttesttesteeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112009 Bug ID: 112009 Summary: testtesttesttesttesttesttesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56235 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56235&action=edit a testtesttesttesttest
[Bug c/112010] New: eeeetesttesttesttesttesteeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112010 Bug ID: 112010 Summary: testtesttesttesttesttesttesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56236 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56236&action=edit aaa testtesttesttesttest
[Bug d/112011] New: eeeetesttesttesttesttesteeeetesttesttesttesttesteeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112011 Bug ID: 112011 Summary: testtesttesttesttesttesttesttesttesttestte sttesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56237 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56237&action=edit c testtesttesttesttest
[Bug bootstrap/112012] New: eeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112012 Bug ID: 112012 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56238 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56238&action=edit testtesttesttesttest
[Bug c/112013] New: eeeetesttesttesttesttesteeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112013 Bug ID: 112013 Summary: testtesttesttesttesttesttesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56239 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56239&action=edit testtesttesttesttest
[Bug analyzer/112014] New: eeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112014 Bug ID: 112014 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56240 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56240&action=edit aa testtesttesttesttesttesttesttesttesttest
[Bug c++/112015] New: eeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112015 Bug ID: 112015 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56241 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56241&action=edit testtesttesttesttest testtesttesttesttesttesttesttesttesttest
[Bug boehm-gc/112016] New: eeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112016 Bug ID: 112016 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: boehm-gc Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56242 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56242&action=edit a testtesttesttesttesttesttesttesttesttest
[Bug analyzer/112017] New: eeeetesttesttesttesttesteeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112017 Bug ID: 112017 Summary: testtesttesttesttesttesttesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56243 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56243&action=edit testtesttesttesttest testtesttesttesttest
[Bug boehm-gc/112018] New: eeeetesttesttesttesttesteeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112018 Bug ID: 112018 Summary: testtesttesttesttesttesttesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: boehm-gc Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56244 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56244&action=edit testtesttesttesttest testtesttesttesttest
[Bug c++/112019] New: eeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112019 Bug ID: 112019 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56245 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56245&action=edit testtesttesttesttest testtesttesttesttest
[Bug c/112020] New: eeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112020 Bug ID: 112020 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56246 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56246&action=edit testtesttesttesttest testtesttesttesttest
[Bug c/112021] New: eeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112021 Bug ID: 112021 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56247 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56247&action=edit aa testtesttesttesttest
[Bug c/112022] New: eeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112022 Bug ID: 112022 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56248 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56248&action=edit azz testtesttesttesttesttesttesttesttesttest
[Bug bootstrap/112023] New: eeeetesttesttesttesttestgg
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112023 Bug ID: 112023 Summary: testtesttesttesttestgg Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56249 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56249&action=edit testtesttesttesttest
[Bug bootstrap/112024] New: azeeeetesttesttesttesttesteeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112024 Bug ID: 112024 Summary: aztesttesttesttesttesttesttesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56250 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56250&action=edit a testtesttesttesttest
[Bug c/112025] New: eeeetesttesttesttesttest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112025 Bug ID: 112025 Summary: testtesttesttesttest Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pi44ude at earningsph dot com Target Milestone: --- Created attachment 56251 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56251&action=edit testtesttesttesttest
[Bug ipa/96503] attribute alloc_size effect lost after inlining
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96503 --- Comment #7 from Martin Uecker --- Am Mittwoch, dem 25.10.2023 um 11:08 + schrieb siddhesh at gcc dot gnu.org: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96503 > > --- Comment #6 from Siddhesh Poyarekar --- > So basically, > > __builtin_with_access(void *ptr, size_t size, int access) > > where access == > > -1: Unknown access semantics > 0: none > 1: read_only > 2: write_only > 3: read_write > > should address both access and alloc_size and even counted_by. Yes, sounds good. > We would need > to emit the builtin in the caller as well as callee of the function that has > the access attribute while for alloc_size, we only need to emit this in the > caller. Yes, makes sense, although I guess caller part for "access" is only for warning and not relevant for BDOS, so could potentially stay as it is for now. For __builtin_with_access we probably only want to allow reducing the object size, while the 'extend_size' workaround used by systemd (cf comment #4) would need to extend it. Maybe we need another flag? Martin
[Bug middle-end/111975] gimple front end can't round-trip vectorized code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111975
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2023-10-25
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
--- Comment #1 from Richard Biener ---
(In reply to Alex Coplan from comment #0)
> Take the following testcase on aarch64:
>
> void foo(int *restrict a, int *restrict b, int *restrict c)
> {
> for (int i = 0; i < 256; i++)
> a[i] = b[i] + c[i];
> }
>
> compiled with -O2 -fdump-tree-optimized-gimple, we get the IR:
>
> void __GIMPLE (ssa,guessed_local(10737416))
> foo (int * restrict a, int * restrict b, int * restrict c)
> {
> sizetype ivtmp.17;
There's __SIZETYPE__ available for this (for portability)
> vector(4) int vect__8.10;
> vector(4) int vect__6.9;
> vector(4) int vect__4.6;
>
> __BB(2,guessed_local(10737416)):
> goto __BB3(precise(134217728));
>
> __BB(3,loop_header(1),guessed_local(687194626)):
> ivtmp.17_23 = __PHI (__BB3: ivtmp.17_19, __BB2: 0ul);
> vect__4.6_9 = MEM [(int *)b_12(D) + ivtmp.17_23 * 1];
It should be __MEM, not sure why that's not (longer?) dumped correctly.
> vect__6.9_27 = MEM [(int *)c_13(D) + ivtmp.17_23 * 1];
> vect__8.10_28 = vect__4.6_9 + vect__6.9_27;
> MEM [(int *)a_14(D) + ivtmp.17_23 * 1] = vect__8.10_28;
> ivtmp.17_19 = ivtmp.17_23 + 16ul;
> if (ivtmp.17_19 != 1024ul)
> goto __BB3(guessed(132120577));
> else
> goto __BB4(guessed(2097151));
>
> __BB(4,guessed_local(10737416)):
> return;
>
> }
>
> but trying to compile this with -fgimple shows several problems:
>
> - the type sizetype isn't known.
> - ivtmp.17 isn't accepted as a variable name (indeed none of the variables
> with . in the name are accepted).
Yeah ... rename them
> - the type vector(4) int isn't understood by the gimple FE.
You need C frontend like typedefs, basically any not basic type needs to be
manually declared (we don't output type declarations when dumping)
> If I fix these issues by declaring the types as follows:
>
> typedef unsigned long sizetype;
> typedef int __attribute__((vector_size(16))) V;
>
> and substituting all uses of the old type names, and also rename all
> variables to replace . with _, then it is nearly accepted. One remaining
> problem seems to be that the MEM syntax isn't accepted:
>
> vect__4_6_9 = MEM [(int *)b_12(D) + ivtmp_17_23 * 1];
>
> gives:
>
> error: 'MEM' undeclared (first use in this function)
>
> and attempting to convert the MEM to use something closer to the syntax in
> the gcc.dg/gimplefe-* tests, this still fails:
>
> vect__4_6_9 = __MEM ((int *)b_12(D) + ivtmp_17_23 * 1);
>
> is rejected with:
>
> error: expected ')' before '*' token
Ah, it's a TARGET_MEM_REF! Parsing that isn't supported. I suggest to
dump before IVOPTs instead.
>
> . It would be good if these issues could be fixed so that optimized gimple
> can be round-tripped without laborious manual fixing of the input. Even with
> that, it's still not clear how to make the MEM expressions here get accepted.
I'll make TARGET_MEM_REF supported.
[Bug middle-end/111975] gimple front end can't round-trip vectorized code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111975
--- Comment #2 from Richard Biener ---
Created attachment 56252
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56252&action=edit
old patch
If you use sth like startswith("vect") you'll figure LC-SSA doesn't work -
here's a quite old patch supporting it (but it was late during stage3 and had
no actual usecase yet).
[Bug c++/99804] cannot convert bit field enum to its own type in a template member function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99804 --- Comment #4 from CVS Commits --- The master branch has been updated by Patrick Palka : https://gcc.gnu.org/g:fb28d5c6b0a47ab704290d0122f978d1e6346551 commit r14-4924-gfb28d5c6b0a47ab704290d0122f978d1e6346551 Author: Patrick Palka Date: Wed Oct 25 09:03:52 2023 -0400 c++: add fixed testcase [PR99804] We accept the non-dependent call f(e) here ever since the NON_DEPENDENT_EXPR removal patch r14-4793-gdad311874ac3b3. I haven't looked closely into why but I suspect wrapping 'e' in a NON_DEPENDENT_EXPR was causing the argument conversion to misbehave. PR c++/99804 gcc/testsuite/ChangeLog: * g++.dg/template/enum9.C: New test.
[Bug c++/99804] cannot convert bit field enum to its own type in a template member function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99804 Patrick Palka changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|--- |14.0 CC||ppalka at gcc dot gnu.org Status|NEW |RESOLVED --- Comment #5 from Patrick Palka --- (In reply to Marek Polacek from comment #3) > Fixed by r14-4793-gdad311874ac3b3, strange. Yay :) thus incidentally fixed for GCC 14.
[Bug d/112026] New: aaaa-te55st-bug-tes55t-aaaaaa12aaaaa-test-bug-test-aaaaaaa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112026 Bug ID: 112026 Summary: -te55st-bug-tes55t-aa12a-test-bug-test-aaa Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56253 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56253&action=edit 1 -te55st-bug-tes55t-aa12a-test-bug-test-aaa
[Bug d/112029] New: aaaaaaaaa12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112029 Bug ID: 112029 Summary: a12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56256 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56256&action=edit a a12
[Bug d/112032] New: aaaaaaaaa12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112032 Bug ID: 112032 Summary: a12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56259 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56259&action=edit a a12
[Bug c/112027] New: aaaa-te55st-bug-tes55t-aaaaaa12aaaaa-test-bug-test-aaaaaaa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112027 Bug ID: 112027 Summary: -te55st-bug-tes55t-aa12a-test-bug-test-aaa Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56254 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56254&action=edit a -te55st-bug-tes55t-aa12a-test-bug-test-aaa
[Bug d/112035] New: aaaaaaaaa12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112035 Bug ID: 112035 Summary: a12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56262 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56262&action=edit a a12
[Bug c++/112030] New: aaaaaaaaa12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112030 Bug ID: 112030 Summary: a12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56257 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56257&action=edit a a12
[Bug c++/112036] New: aaaaaaaaa12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112036 Bug ID: 112036 Summary: a12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56263 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56263&action=edit a a12
[Bug c/112042] New: aaaaaaaaa12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112042 Bug ID: 112042 Summary: a12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: mariaa at partmed dot net Target Milestone: --- a12
[Bug d/112028] New: aaaaaaaaa12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112028 Bug ID: 112028 Summary: a12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56255 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56255&action=edit a a12
[Bug d/112033] New: aaaaaaaaa12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112033 Bug ID: 112033 Summary: a12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56260 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56260&action=edit a a12
[Bug c++/112031] New: aaaaaaaaa12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112031 Bug ID: 112031 Summary: a12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56258 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56258&action=edit a a12
[Bug c++/112037] New: aaaaaaaaa12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112037 Bug ID: 112037 Summary: a12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56264 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56264&action=edit a a12
[Bug c/112040] New: aaaaaaaaa12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112040 Bug ID: 112040 Summary: a12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56267 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56267&action=edit a a12
[Bug c/112034] New: aaaaaaaaa12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112034 Bug ID: 112034 Summary: a12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56261 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56261&action=edit a a12
[Bug c++/112038] New: aaaaaaaaa12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112038 Bug ID: 112038 Summary: a12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mariaa at partmed dot net Target Milestone: --- Created attachment 56265 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56265&action=edit a a12
