https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103054
Bug ID: 103054
Summary: [f18] Gfortran accepts invalid and rejects valid
co_reduce argument keyword name
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Sever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103053
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103053
--- Comment #1 from Andrew Pinski ---
>.globl __divti3
> even though there is no call to that function.
Yes it does no harm to emit it though.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103053
Bug ID: 103053
Summary: Unexpected ".global __divti3" emitted for unsigned 128
bit division
Product: gcc
Version: 10.3.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102049
--- Comment #4 from Eric Gallager ---
(In reply to Marek Polacek from comment #3)
> Closing due to not enough interest.
>
> My patch was:
> https://gcc.gnu.org/pipermail/gcc-patches/2021-September/580179.html
Wait, I was interested!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100937
Eric Gallager changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103029
luoxhu at gcc dot gnu.org changed:
What|Removed |Added
CC||ro at gcc dot gnu.org
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103041
luoxhu at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103044
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #18 from CVS Commits ---
The master branch has been updated by Jan Hubicka :
https://gcc.gnu.org/g:62af7d9402f551fa708125fafed2950d8912b25e
commit r12-4857-g62af7d9402f551fa708125fafed2950d8912b25e
Author: Jan Hubicka
Date: Wed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103015
--- Comment #8 from Iain Buclaw ---
(In reply to Iain Buclaw from comment #6)
> Not that there's a regressing commit anywhere, just a change exposed a
> problem with Solaris.
First commit it started occurring with -O2 -ftree-vectorize is r10-47
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103048
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2021-11-02
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103052
Andrew Pinski changed:
What|Removed |Added
Known to fail||10.3.0, 11.2.0
--- Comment #6 from Andr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103052
Andrew Pinski changed:
What|Removed |Added
Component|middle-end |ipa
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103052
--- Comment #4 from Tor Andersson ---
I can make it succeed with -O1 if I add the -fipa-pure-const flag, if that can
help tracking down.
$ gcc -O1 xxx.c && ./a.out
FAIL: should NOT get here :(
$ gcc -O1 -fno-ipa-pure-const xxx.c && ./a.out
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103052
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |9.5
Summary|Function call om
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103052
Andrew Pinski changed:
What|Removed |Added
Keywords||wrong-code
Component|c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103052
--- Comment #2 from Tor Andersson ---
Same problem with gcc-11.
$ gcc-11 -O1 xxx.c && ./a.out
FAIL: should NOT get here :(
$ gcc-11 -v
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc-11
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103052
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103052
Bug ID: 103052
Summary: Function call omitted at -O1 optimization level.
Product: gcc
Version: 10.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103051
Bug ID: 103051
Summary: [12 regression] new test case
gcc.dg/vect/tsvc/vect-tsvc-s112.c fails in r12-4840
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #17 from hubicka at kam dot mff.cuni.cz ---
> Great, I will take a look now (I was travelling that is why i did not
> started earlier)
Found it - there is a thinko in way NOT_RETURNED flag is handled in the
call statement analysis. I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #16 from hubicka at kam dot mff.cuni.cz ---
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
>
> --- Comment #15 from Iain Buclaw ---
> Got it. The difference between D and C++ is a matter of early inlining.
>
> The C++ exampl
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
>
> --- Comment #15 from Iain Buclaw ---
> Got it. The difference between D and C++ is a matter of early inlining.
>
> The C++ example Jakub posted fails in the same way that D does if you compile
> with: -O1 -fno-inline
Great, I will take a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #15 from Iain Buclaw ---
Got it. The difference between D and C++ is a matter of early inlining.
The C++ example Jakub posted fails in the same way that D does if you compile
with: -O1 -fno-inline
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102049
Marek Polacek changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103050
Martin Liška changed:
What|Removed |Added
Priority|P3 |P1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103050
--- Comment #10 from Martin Liška ---
Alternatively, one can see the memory corruption during LTO bootstrap in Go
library build:
$ ../configure --enable-languages=c,c++,lto,go --disable-multilib
--disable-libsanitizer --with-build-config=bootst
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #14 from Iain Buclaw ---
(In reply to hubicka from comment #13)
> > See above comments from Iain, even if that pre-initialization is removed it
> > is
> > still miscompiled. And, the testcase fails not because of the padding bits
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97376
Patrick Palka changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103050
--- Comment #9 from Martin Liška ---
... where mod_ref_flags are:
(gdb) p modref_flags
$15 = 247
and
(gdb) p modref_flags
$18 = 22
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103050
--- Comment #8 from Martin Liška ---
So the only 2 transform happen here:
(gdb) bt
#0 gimple_call_retslot_flags (stmt=0x74543b40) at
/home/marxin/Programming/gcc/gcc/gimple.c:1644
#1 0x00ff6128 in handle_rhs_call (stmt=0x74543
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103050
--- Comment #7 from Martin Liška ---
$ grep dbgcnt omn*
omnetpp_r.ltrans0.ltrans.140t.pre:***dbgcnt: lower limit 1296 reached for
ipa_mod_ref_pta.***
omnetpp_r.ltrans0.ltrans.140t.pre:***dbgcnt: upper limit 1296 reached for
ipa_mod_ref_pta.***
o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #13 from hubicka at kam dot mff.cuni.cz ---
> See above comments from Iain, even if that pre-initialization is removed it is
> still miscompiled. And, the testcase fails not because of the padding bits
> not
> being zero, but becaus
> See above comments from Iain, even if that pre-initialization is removed it is
> still miscompiled. And, the testcase fails not because of the padding bits
> not
> being zero, but because the address of self stored into one of the fields
> isn't
> there or modref thinks it can't be changed or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101764
Patrick Palka changed:
What|Removed |Added
CC||c.de-claverie at pm dot me
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96815
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
St
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103050
--- Comment #6 from Martin Liška ---
I was able to track that to ltrans0, where one needs 2 optimizations to happen:
-fdbg-cnt=ipa_mod_ref_pta:1296-1296:1482-1482
then optimized dump differs (good vs. bad) in:
void recordScalar (struct cFileOu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #12 from Jakub Jelinek ---
(In reply to Jan Hubicka from comment #11)
> Sorry for the breakage.
>
> Looking at Jakub's comment:
> SR.11_24 = 0;
> _12 = SR.11_24;
> MEM [(unsigned char * {ref-all})&nrvo] = _12;
> nrvo = nrvo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103030
--- Comment #4 from c25devbiz at aol dot com ---
it works with -mpc64
so the default was set to the highest, but I guess should have been limited by
the target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103041
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #1 from luoxhu at gcc dot gnu.org ---
> Could you please verify whether it is caused by r12-4818 instead of r12-4819?
> r12-4819 is a NFC patch which seems more unlikely,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103050
--- Comment #5 from Martin Liška ---
This one is real:
Running simulation...
** Event #1 T=0 Elapsed: 0.000s (0m 00s) 0% completed ev/sec=0
** Event #2160226 T=0.003 Elapsed: 0.000s (0m 00s) 100% completed
ev/sec=0
Simulation ti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103050
--- Comment #4 from Martin Liška ---
(In reply to Martin Liška from comment #3)
> First valgrind error happens here:
>
> Loading NED files from a SPEC directory 13
> ==22550== Conditional jump or move depends on uninitialised value(s)
> ==22550
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103050
--- Comment #3 from Martin Liška ---
First valgrind error happens here:
Loading NED files from a SPEC directory 13
==22550== Conditional jump or move depends on uninitialised value(s)
==22550==at 0x53DF91: Cmdenv::sputn(char const*, int) (c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98490
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||krefson at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103045
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103050
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2021-11-02
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103050
--- Comment #1 from Jan Hubicka ---
Martin,
do we know that the retslot change is the bad commit? I proofread the patch
and did not see anything obviously wrong, however as seen in PR103040 the
previous behaviour that made return slots to escap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
Jan Hubicka changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103033
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103050
Bug ID: 103050
Summary: [12 Regression] 520.omnetpp_r miscompiled after
r12-4787-gb8ef019ab938471f
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: wro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100937
frankhb1989 at gmail dot com changed:
What|Removed |Added
CC||frankhb1989 at gmail dot c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103033
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONF
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103033
--- Comment #2 from qinzhao at gcc dot gnu.org ---
I can repeat this ICE on the gcc farm machine gcc112, which is a Powerpcle
linux machine with the latest upstream gcc (11/2/2021).
and locate the issue at:
Breakpoint 2, expand_DEFERRED_INIT (s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103041
--- Comment #3 from Richard Biener ---
The dup was fixed, please close as duplicate in case the sparc issue goes away
as well.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103029
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103029
--- Comment #6 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:164bbf701ff10ff44e272525e8f462ed3ff1cf43
commit r12-4850-g164bbf701ff10ff44e272525e8f462ed3ff1cf43
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94376
Patrick Palka changed:
What|Removed |Added
Last reconfirmed||2021-11-02
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103049
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93989
--- Comment #8 from Jonathan Wakely ---
Further reduced:
struct bstring
{
char buf {};
char* ptr = buf;
};
void test01()
{
constexpr bstring v1{};
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93989
Jonathan Wakely changed:
What|Removed |Added
Keywords||diagnostic
--- Comment #7 from Jonatha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103049
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103049
Bug ID: 103049
Summary: [C++23] P0849R8 - auto(x): decay-copy in the language
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93989
--- Comment #6 from Jonathan Wakely ---
This works fine, i.e. just remove the constexpr specifiers on the local
variables:
consteval void test01()
{
typedef constexpr_allocator alloc_type;
typedef bstring test_type;
alloc_type a1(1);
tes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103041
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103029
--- Comment #5 from Richard Biener ---
The gimple_lv_adjust_loop_header_phi comment isn't relevant but what is is the
association between PHI node argument and SLP node index from the analysis
phase,
in particular for backedges. See vect_schedu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103025
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103038
--- Comment #6 from qinzhao at gcc dot gnu.org ---
just wondering why the ICE after my fix to PR102281. and found the reason:
Before the fix to PR102281, the IR before expansion phase is:
void test ()
{
<<< Unknown tree: offset_type >>> PtrMe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103046
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |11.3
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103048
--- Comment #1 from songyuanyao ---
https://timsong-cpp.github.io/cppwp/except#throw-5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103048
Bug ID: 103048
Summary: Mandatory copy elision used for catch-by-value
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103011
Pekka S changed:
What|Removed |Added
CC||p...@gcc-bugzilla.mail.kaps
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #10 from Iain Buclaw ---
(In reply to Iain Buclaw from comment #8)
> Still occurs after stubbing out the build_memset_call function in the D
> front-end. Just having a look at the this reference parameter now.
Switched the return v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103037
--- Comment #6 from rguenther at suse dot de ---
On Tue, 2 Nov 2021, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103037
>
> --- Comment #5 from Jakub Jelinek ---
> We have:
> var_3.2_4 = var_3;
> iftmp.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103047
Bug ID: 103047
Summary: Inconsist arguments ordering for inlined subroutine
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103027
--- Comment #3 from David Malcolm ---
For reference, here's a patch to clang-tidy for this (currently under review):
https://reviews.llvm.org/D112916
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103046
Bug ID: 103046
Summary: Incorrect debug info for uint128 bit shift in gcc 11.2
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103006
--- Comment #10 from rguenther at suse dot de ---
On Tue, 2 Nov 2021, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103006
>
> Jakub Jelinek changed:
>
>What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #9 from Iain Buclaw ---
Confirmed that r12-4814 is the first commit when this FAIL started to occur.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 103007, which changed state.
Bug 103007 Summary: [12 Regression] ice in vect_normalize_conj_loc, at
tree-vect-slp-patterns.c:722 since
r12-4785-ged3de62ac949c92ad41ef6de7cc926fbb2a510ce
https://gcc.gnu.org/bugzilla/show_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103007
Tamar Christina changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103007
--- Comment #11 from CVS Commits ---
The master branch has been updated by Tamar Christina :
https://gcc.gnu.org/g:6cc8aa65fdeaefe9774d5e0d4e72c91f52313be1
commit r12-4846-g6cc8aa65fdeaefe9774d5e0d4e72c91f52313be1
Author: Tamar Christina
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103038
--- Comment #5 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:268b43d2592c196ea101946d7063156a914b2713
commit r12-4845-g268b43d2592c196ea101946d7063156a914b2713
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103038
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102975
Patrick Palka changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103045
Dominique d'Humieres changed:
What|Removed |Added
Last reconfirmed||2021-11-02
Status|UN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103015
--- Comment #7 from Iain Buclaw ---
(In reply to Iain Buclaw from comment #6)
> Not that there's a regressing commit anywhere, just a change exposed a
> problem with Solaris.
First commit it started occurring with -O2 is r12-4240.
This gives an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102912
--- Comment #2 from Jonathan Wakely ---
This is a bit of a mess. Previously we didn't construct the correct member of
the union in _-variant_construct_single, we just plopped an object in the
memory occupied by the union:
void* __storage = st
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103045
Bug ID: 103045
Summary: False report substring out of bounds with
-fbounds-check
Product: gcc
Version: 10.3.0
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102505
Martin Jambor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #8 from Iain Buclaw ---
Still occurs after stubbing out the build_memset_call function in the D
front-end. Just having a look at the this reference parameter now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103041
--- Comment #1 from luoxhu at gcc dot gnu.org ---
Could you please verify whether it is caused by r12-4818 instead of r12-4819?
r12-4819 is a NFC patch which seems more unlikely, and r12-4818 also ICEs in
PR103029, it is possibly a duplicate of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103044
Bug ID: 103044
Summary: d: Use __builtin_clear_padding for zeroing objects
before set.
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #7 from Iain Buclaw ---
(In reply to Jakub Jelinek from comment #6)
> One quite visible change is that D has those stmts that clear the vars
> before it is constructed, so e.g. in main:
> SR.11_24 = 0;
> _12 = SR.11_24;
> MEM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103043
--- Comment #3 from Thomas ---
thank you for the quick response. I am very new here and did not immediately
see that this was already discussed.
Does this mean you have to wait for an update from Apple or is there a
workaround?
many thanks
Thoma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #6 from Jakub Jelinek ---
One quite visible change is that D has those stmts that clear the vars before
it is constructed, so e.g. in main:
SR.11_24 = 0;
_12 = SR.11_24;
MEM [(unsigned char * {ref-all})&nrvo] = _12;
nrvo = n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #5 from Jakub Jelinek ---
So the question is what is different between the C++ and D version.
In C++17, RVO is mandatory, NRVO is an optimization, but guess one could add a
copy constructor that would set impl to this and copy over x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102992
Dominique d'Humieres changed:
What|Removed |Added
CC||gccbug at duemmels dot de
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103043
Dominique d'Humieres changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103043
--- Comment #1 from Andrew Pinski ---
There is a dup of this already and it is a bug in Mac os where deconstructs are
not run.
1 - 100 of 167 matches
Mail list logo
