https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104659
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104729
--- Comment #1 from Iain Buclaw ---
These should be templated functions so that they get compiled in.
The betterc tests build without linking in libphobos, however many version
paths define a new symbol.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104735
--- Comment #1 from Iain Buclaw ---
The test could implement signbit inline.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104736
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104737
Iain Buclaw changed:
What|Removed |Added
URL||https://issues.dlang.org/sh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104738
Iain Buclaw changed:
What|Removed |Added
URL||https://issues.dlang.org/sh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104740
--- Comment #1 from Iain Buclaw ---
b18489.d and ice21727.d were fixed in the last sync (r12-7414).
Only simd_ctfe.d is outstanding.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104743
--- Comment #1 from Iain Buclaw ---
Does anything change if you compile the test with
`-ftrivial-auto-var-init=zero` ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104737
--- Comment #2 from Iain Buclaw ---
Fixed test was downstreamed in r12-7454.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104737
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104735
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104729
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104741
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104744
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104749
--- Comment #6 from Iain Buclaw ---
Just having a look around, I couldn't see anywhere that `___s` would be created
now.
Then I came across r9-8460, which was fixed for 10.1.0, and backported before
9.4.0 was released. Linked bug report is pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104743
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104745
--- Comment #1 from Iain Buclaw ---
*** Bug 104743 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104745
--- Comment #2 from Iain Buclaw ---
Regression confirmed in upstream druntime. The `itemSize' reported by a
struct's TypeInfo need not be a multiple of pointer size.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104742
Iain Buclaw changed:
What|Removed |Added
See Also||https://issues.dlang.org/sh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104538
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104835
Iain Buclaw changed:
What|Removed |Added
CC||syq at debian dot org
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104835
--- Comment #2 from Iain Buclaw ---
The backtrace I get is:
d21: internal compiler error: output_operand: '%l' operand isn't a label
0x1208268cf output_operand_lossage(char const*, ...)
../../gcc/final.cc:3235
0x12082692b output_asm_lab
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104835
--- Comment #3 from Iain Buclaw ---
Ends with:
#86 0x000120582768 in semantic3(Dsymbol*, Scope*) (sc=,
dsym=) at ../../gcc/d/dmd/semantic3.d:1525
#87 Semantic3Visitor::visit(AggregateDeclaration*) (this=0xffbab0,
ad=0xfff76c0800) a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104835
Iain Buclaw changed:
What|Removed |Added
See Also||https://github.com/dlang/dm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104738
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104835
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104742
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104745
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104911
--- Comment #2 from Iain Buclaw ---
That's interesting. I've just done a build of
54ef95cc4d1f3f2cde7c1f13250f889ffb81ca75 (20220301) and I get the same
comparison failure.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104911
--- Comment #5 from Iain Buclaw ---
(In reply to Rainer Orth from comment #4)
> typesem.s indeed shows small codegen differences, while for semantic3.s
> there are
> both codegen differences per se as well as label renamings that may not
> effec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104911
--- Comment #6 from Iain Buclaw ---
Created attachment 52649
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52649&action=edit
fdump-tree-original
The corrupt is indeed coming from the front-end.
Attached tree dumps.
--- stage2/typesem.d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104911
Iain Buclaw changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105004
Bug ID: 105004
Summary: d: internal compiler error: in build_complex, at
tree.c:2358
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104911
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105004
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104878
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104740
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105942
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106555
Bug ID: 106555
Summary: [12/13 Regression] d: internal compiler error: in
add_stack_var, at cfgexpand.cc:476
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Sev
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106555
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106563
Bug ID: 106563
Summary: [12/13 Regression] d: undefined reference to
pragma(inline) symbol
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106563
Iain Buclaw changed:
What|Removed |Added
Known to fail||12.1.0
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106563
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105360
--- Comment #2 from Iain Buclaw ---
Looks like it's a middle-end missed-optimization, not a D front-end one.
https://godbolt.org/z/5WWYEG4jW
Perhaps we need an extra DCE pass?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105360
Iain Buclaw changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104317
--- Comment #3 from Iain Buclaw ---
(In reply to Siarhei Siamashka from comment #2)
> I first tried to toggle "flag_weak_templates" in "gcc/d/lang.opt" from 1 to
> 0 in GDC11 instead of reverting PR99914, but the resulting toolchain was
> unable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102765
--- Comment #6 from Iain Buclaw ---
r13-2002 (and r12-8673) is a start that sows the seeds to make the codegen
option -fno-weak-templates the default. Should just be a case of extending the
forced emission to all instantiations too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106623
Bug ID: 106623
Summary: internal compiler error: Segmentation fault at
gimple-expr.cc:88
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106623
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106638
--- Comment #2 from Iain Buclaw ---
(In reply to Martin Liška from comment #1)
> Should likely lead to something like:
> https://github.com/dlang/DIPs/blob/master/DIPs/accepted/DIP1021.md
Indeed, I'm sure the wiki links were working at one point
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106638
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106819
Bug ID: 106819
Summary: [13 Regression] NaN != NaN comparisons return false at
-O2 since r13-2338
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: norm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106832
--- Comment #10 from Iain Buclaw ---
(In reply to Peter Bergner from comment #9)
> (In reply to Jakub Jelinek from comment #2)
> > Well, I certainly see libphobos/configure.tgt having powerpc*-linux* as the
> > only target that does:
> > power
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106832
--- Comment #12 from Iain Buclaw ---
(In reply to Jakub Jelinek from comment #11)
> Doesn't powerpc*-*-freebsd* use IEEE double long double?
> grep LONG_DOUBLE_SIZE *
> darwin.h:#define RS6000_DEFAULT_LONG_DOUBLE_SIZE 128
> linux64.h:#define RS6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106832
--- Comment #24 from Iain Buclaw ---
(In reply to Peter Bergner from comment #22)
> (In reply to Peter Bergner from comment #21)
> > For the record, this is what I'm testing with:
>
> So we get farther, but ICE again at:
> /home/bergner/gcc/gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106832
--- Comment #25 from Iain Buclaw ---
(In reply to Iain Buclaw from comment #24)
> I'd imagine all static asserts would be hit, so a lot more than that -
> floor, tan, sin, cos, pow, etc... - some of which are not exactly trivial to
> implement f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107101
Bug ID: 107101
Summary: d: Add stub for object module when libphobos is not
compiled, or supported
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: nor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107101
--- Comment #1 from Iain Buclaw ---
This also affects when compiling with `-nostdinc`.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102765
Iain Buclaw changed:
What|Removed |Added
CC||witold.baryluk+gcc at gmail
dot co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107241
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107265
Bug ID: 107265
Summary: error: TARGET_VXWORKS7 was not declared in this scope;
did you mean TARGET_VXWORKS
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Sever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103728
--- Comment #3 from Iain Buclaw ---
(In reply to Pierrick Bouvier from comment #2)
> Problem with command line approach is that it implies to patch all our
> scripts, which is *really* boring. At this point, manually adding rt_options
> string i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103839
Bug ID: 103839
Summary: __builtin_clear_padding doesn't zero alignment holes
of unions with fields that overlap padding
Product: gcc
Version: 12.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103839
--- Comment #1 from Iain Buclaw ---
(In reply to Iain Buclaw from comment #0)
> I can work around this by setting DECL_PADDING_P on all fields in unions
> except the first. However I suspect this is a mistake, and the proper thing
> to do would
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103839
--- Comment #3 from Iain Buclaw ---
(In reply to Jakub Jelinek from comment #2)
> For __builtin_clear_padding builtin, that behavior is completely
> intentional, for unions the compiler most of the time doesn't know which
> union member is curre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840
Bug ID: 103840
Summary: d: Errors message: Please submit a full bug report in
testsuite
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840
--- Comment #1 from Iain Buclaw ---
In both cases, the dmd front-end has an error with %zu as a format specifier in
the message.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840
--- Comment #2 from Iain Buclaw ---
Fix in upstream.
https://github.com/dlang/dmd/pull/13462
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103944
Iain Buclaw changed:
What|Removed |Added
Target||i686-redhat-linux
--- Comment #3 from Iai
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103944
--- Comment #6 from Iain Buclaw ---
(In reply to Jakub Jelinek from comment #4)
> Note, it isn't just i686-linux, I was getting the hangs on x86_64-linux,
> s390x-linux or armv7hl-linux-gnueabi too.
> Wonder whether it is
> -fstack-clash-protect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103944
--- Comment #7 from Iain Buclaw ---
(In reply to Iain Buclaw from comment #6)
> (In reply to Jakub Jelinek from comment #4)
> > Note, it isn't just i686-linux, I was getting the hangs on x86_64-linux,
> > s390x-linux or armv7hl-linux-gnueabi too
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552
Iain Buclaw changed:
What|Removed |Added
CC||ibuclaw at gdcproject dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103015
--- Comment #5 from Iain Buclaw ---
(In reply to Richard Biener from comment #4)
> I suppose that maybe solaris does not align TLS vars with custom DECL_ALIGN
> properly, but maybe you also did not have g:eed248bb8cc3091e8 in your tree?
I'm on r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103015
--- Comment #6 from Iain Buclaw ---
(In reply to Iain Buclaw from comment #5)
> (In reply to Richard Biener from comment #4)
> > I suppose that maybe solaris does not align TLS vars with custom DECL_ALIGN
> > properly, but maybe you also did not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
--- Comment #3 from Iain Buclaw ---
The test is trivially translatable into C++, though I don't think C++ attempts
to ensure (n)rvo always occurs.
---
#include
struct S101273
{
int x;
S101273* impl;
S101273(int x)
{
th
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=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 #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=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=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=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=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=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=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=103040
--- Comment #20 from Iain Buclaw ---
I don't see any failures for this test anymore, so inclined to say yes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102765
--- Comment #2 from Iain Buclaw ---
D semantics for template symbols is that they must be overridable - even by
normal global symbols.
So in version 11.1, the default linkage for templates was switched over to
weak, and with that, you can't saf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103120
Bug ID: 103120
Summary: [12 Regression] test miscompiled with -O2 on darwin
since r12-4790
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103120
Iain Buclaw changed:
What|Removed |Added
Target|x86_64-lin ux-gnu |x86_64-linux-gnu,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103520
Iain Buclaw changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103529
--- Comment #2 from Iain Buclaw ---
Hi Rainer,
I pushed a fix for this a couple weeks back, just haven't trickled it down yet.
https://issues.dlang.org/show_bug.cgi?id=22517
https://github.com/dlang/dmd/pull/13324
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103528
--- Comment #3 from Iain Buclaw ---
(In reply to Rainer Orth from comment #2)
> Created attachment 51921 [details]
> libphobos: Define SIG_BLOCK etc. on Solaris [PR 103528]
>
> Define SIG_BLOCK and friends on Solaris to unbreak bootstrap.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103558
--- Comment #1 from Iain Buclaw ---
Fix is already in upstream, just needs to be merged in.
https://github.com/dlang/druntime/pull/3620
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103582
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103558
Iain Buclaw changed:
What|Removed |Added
CC||doko at debian dot org
--- Comment #2 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103558
Iain Buclaw changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103529
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100062
Iain Buclaw changed:
What|Removed |Added
Component|middle-end |d
--- Comment #3 from Iain Buclaw ---
Sw
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103577
--- Comment #2 from Iain Buclaw ---
(In reply to r...@cebitec.uni-bielefeld.de from comment #1)
> I cannot yet tell if this is just an issue with GCC 11.1.0 gdc or
> libphobos that's fixed in 11.2.0 or gcc-11 branch.
It could be this patch fix
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103577
--- Comment #3 from Iain Buclaw ---
FYI, with darwin, I've only been using the most recent commit in
releases/gcc-11 for testing as there have been a number of issues exposed from
that port.
I have VMs set-up running 10.4 (PPC), 10.6 (x86_64),
101 - 200 of 327 matches
Mail list logo
