https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98838
--- Comment #2 from Jonathan Wakely ---
Indeed: https://gcc.gnu.org/pipermail/gcc-bugs/2021-January/727161.html
It was discussed when we moved to the new list software and it was suggested
that simply replacing "@" with " at " and ".com" with "
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98798
--- Comment #3 from Jonathan Wakely ---
(In reply to Martin Liška from comment #2)
> I think it's a bug in libstdc++ and one can see it with valgrind:
But there's no error when compiled with clang and libstdc++, so that suggests
the problem is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98798
--- Comment #5 from Jonathan Wakely ---
I wonder if https://itanium-cxx-abi.github.io/cxx-abi/abi.html#array-cookies
needs to be updated for aligned new[] expressions, or if G++ is just not
accounring for them correctly.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98798
--- Comment #8 from Jonathan Wakely ---
I've reported this as https://github.com/itanium-cxx-abi/cxx-abi/issues/119 but
I haven't tried to fix the spec, or fix G++.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98798
--- Comment #6 from Jonathan Wakely ---
Yes, I think the ABI needs fixing. In this example Foo has a trivial destructor
and Foo::operator delete[](void*, size_t, align_val_t) does not have two
parameters. According to the ABI, no cookie is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98841
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2021-01-26
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98840
--- Comment #1 from Jonathan Wakely ---
The ABI requires it. The caller is responsible for constructing and destroying
the argument.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98840
--- Comment #2 from Jonathan Wakely ---
https://www.youtube.com/watch?v=rHIkrotSwcc discusses exactly this problem.
See also https://quuxplusone.github.io/blog/2018/05/02/trivial-abi-101/
This is not a GCC bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98842
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98861
--- Comment #1 from Jonathan Wakely ---
(In reply to cqwrteur from comment #0)
> The mailing list requires me to request the feature here. I put it here.
> https://www.mail-archive.com/gcc@gcc.gnu.org/msg94104.html
> "However, I desperately
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58909
--- Comment #15 from Jonathan Wakely ---
And the static libc++.a doesn't use weak symbols, so you need to link to
libpthread youself, and the necessary symbols get pulled in correctly.
The problem for libstdc++.a is that the weak symbols do not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92546
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|10.3|12.0
Summary|[10/11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98861
--- Comment #10 from Jonathan Wakely ---
(In reply to cqwrteur from comment #3)
> Relying on stdio.h even stdio.h is not freestanding.
Nonsense.
(In reply to cqwrteur from comment #4)
> BTW. std::terminate() is not thread-safe which is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98861
--- Comment #13 from Jonathan Wakely ---
(In reply to cqwrteur from comment #11)
> Functions without thread-safety are always terrible. Like all functions in
> cctype. They should be avoided like plague.
It's thread-safe though. What are you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58909
--- Comment #18 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #17)
> (In reply to Jakub Jelinek from comment #16)
> The example in comment 0 fails on Fedora. Nothing in libstdc++.a causes
> anything from libpthread.o to be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98861
--- Comment #22 from Jonathan Wakely ---
(In reply to cqwrteur from comment #20)
> 1. Freestanding C++ in the current situation is very problematic. (You do
> not have memcpy, you do not have std::move. You do not have std::forward.
> You do not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58909
--- Comment #22 from Jonathan Wakely ---
In that case it finds the no-op symbol in libc.so.6 and doesn't crash.
$ g++ cv.C -g -Wl,--trace-symbol=pthread_cond_destroy
/usr/bin/ld: /lib64/libc.so.6: definition of pthread_cond_destroy
This
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98861
--- Comment #15 from Jonathan Wakely ---
> > (In reply to cqwrteur from comment #12)
> > > stdio.h should not get included in any circumstances for EH. You are
> > > implementing the operating system, but you need to enable EH by the
> > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58909
--- Comment #17 from Jonathan Wakely ---
(In reply to Jakub Jelinek from comment #16)
> Are those weak refs from libstdc++.a objects or from the user *.o files?
>From libstdc++.a
> If the former, perhaps we could declare some libstdc++ APIs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98861
--- Comment #19 from Jonathan Wakely ---
(In reply to cqwrteur from comment #16)
> That does not work in the real-world since your libstdc++'s freestanding
> header never works correctly, (you get compilation errors).
Try reporting a bug about
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98861
--- Comment #21 from Jonathan Wakely ---
(In reply to cqwrteur from comment #20)
> (In reply to Jonathan Wakely from comment #19)
> > (In reply to cqwrteur from comment #16)
> > > That does not work in the real-world since your libstdc++'s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98861
--- Comment #26 from Jonathan Wakely ---
(In reply to cqwrteur from comment #24)
> (In reply to Jonathan Wakely from comment #22)
> > (In reply to cqwrteur from comment #20)
> > > 1. Freestanding C++ in the current situation is very problematic.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58909
--- Comment #20 from Jonathan Wakely ---
I don't think so. The linker just doesn't resolve the undefined weak symbol for
pthread_cond_destroy is left equal to zero, and so there's a segfault when it
gets called.
$ g++ cv.C -static -g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98884
Jonathan Wakely changed:
What|Removed |Added
Component|c++ |target
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58354
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |10.2
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17314
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55120
--- Comment #9 from Jonathan Wakely ---
(In reply to Nick Krempel from comment #0)
> The following code should fail to compile but does not:
>
> struct V {};
> struct B : private virtual V {};
> struct D : B {};
>
> int main() {
> D d;
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55120
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97202
--- Comment #6 from Jonathan Wakely ---
If the invalid special member is defined out of the class body, you get another
error:
template
struct F
{
F();
};
template
inline F::F() { }
101032.C:4:8: error: expected unqualified-id before ‘)’
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101033
Jonathan Wakely changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101033
Jonathan Wakely changed:
What|Removed |Added
Keywords||diagnostic
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101034
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101032
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97202
Jonathan Wakely changed:
What|Removed |Added
CC||kevin.c.eady at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101052
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2021-06-14
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101055
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101055
Jonathan Wakely changed:
What|Removed |Added
See Also||http://bugzilla.opensuse.or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101049
--- Comment #1 from Jonathan Wakely ---
I don't see how this can be done in the library though, so component=libstdc++
seems wrong.
Probably a dup of PR 86912
See also PR 78113
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101055
Jonathan Wakely changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101056
Jonathan Wakely changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101055
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |11.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101055
Jonathan Wakely changed:
What|Removed |Added
Known to work||10.3.0
Summary|should use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101060
Jonathan Wakely changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100894
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |10.4
--- Comment #1 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101052
Jonathan Wakely changed:
What|Removed |Added
Keywords||patch
--- Comment #2 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101034
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |9.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100894
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101052
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |12.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101052
Jonathan Wakely changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101087
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101029
--- Comment #8 from Jonathan Wakely ---
It's only fixed on trunk so far, which will become the 12.1 release in 10-11
months.
It's a regression, so either the compiler fix should get backported to the
release branches (including the gcc-10
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101095
Bug ID: 101095
Summary: Bogus "error: conflicting global module declaration"
for abbreviate function template using placeholder
type in noexcept
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101095
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100475
--- Comment #8 from Jonathan Wakely ---
We should almost never use list-init in the library unless the standard
explicitly specifies it. Even if the standard specifies it, we should consider
whether that's a defect in the standard. Uniform init
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100982
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91910
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100990
Bug ID: 100990
Summary: Iterator checks for Debug Mode cannot be used with a
non-common range
Product: gcc
Version: 11.1.1
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90704
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |INVALID
Status|SUSPENDED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100992
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Component|c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100982
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |9.5
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100825
--- Comment #9 from Jonathan Wakely ---
As comment 7 already said.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101015
Bug ID: 101015
Summary: Poor diagnostic for deprecated alias-declaration
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101006
Jonathan Wakely changed:
What|Removed |Added
Blocks||67491
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101006
Jonathan Wakely changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92806
--- Comment #1 from Jonathan Wakely ---
This seems to be fixed now:
a.C:8:9: required by the constraints of 'template concept foo'
a.C:8:25: error: constraint 'trait::value [with T = int]' has type
'trait::', not 'bool'
8 | concept foo =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97407
--- Comment #4 from Jonathan Wakely ---
See also PR 89370 comment 2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101113
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2021-06-17
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101106
Jonathan Wakely changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101106
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2021-06-17
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100823
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101136
--- Comment #2 from Jonathan Wakely ---
This is because the _GLIBCXX_USE_WCHAR_T macro is not defined, because
etc are not complete on the target, so we don't have e.g. wcslen and
other wchar_t functions.
However, the wchar_t type is always
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101137
--- Comment #2 from Jonathan Wakely ---
And ideally, remove everything not relevant to the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101137
--- Comment #3 from Jonathan Wakely ---
I get the same behaviour if I replace all uses of std::conjunction with fold
expressions and split up your unreadable long lines into simpler atoms (which
also makes the code much simpler) e.g.
template
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89417
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |WONTFIX
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101137
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2021-06-21
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43933
--- Comment #5 from Jonathan Wakely ---
It's not fixed in GCC 9 though. I think it's probably fixed by r11-2546 for PR
94024 but I can't bisect right now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101137
--- Comment #4 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #3)
> template
> concept SignedIntegralRef1
> = std::is_lvalue_reference_v && SignedIntegral1;
Oops, that should be
std::is_lvalue_reference_v &&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101179
--- Comment #1 from Jonathan Wakely ---
On IRC Richi said: "VRP has code to do that but maybe for some reason shifts
are not handled"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101179
Bug ID: 101179
Summary: y % (x ? 16 : 4) and y % (4 << (2 * (bool)x)) produce
different code
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101179
--- Comment #3 from Jonathan Wakely ---
the ?: one seems to produce better code currently though, so I'm not sure
transforming it to the shift is what we want.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101164
--- Comment #4 from Jonathan Wakely ---
For example, the C++ front end has to be prepared to handle this:
struct S {
int i;
decltype(i) j;
int k[sizeof(i)];
};
The C++ compiler has to keep track of every name from its point of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101137
Jonathan Wakely changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101136
--- Comment #3 from Jonathan Wakely ---
Oh it wasn't last year, it was January this year. There's a patch at
https://gcc.gnu.org/pipermail/libstdc++/2021-January/051868.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101198
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2021-06-24
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80504
--- Comment #5 from Jonathan Wakely ---
Huh, what I actually committed doesn't match the changelog. Oops.
But what I committed is better anyway.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101203
--- Comment #2 from Jonathan Wakely ---
We also can't guarantee that the address of the new function is unique across
shared libraries, making the test in _M_equal unreliable. The technique in
std::any has a fallback to using RTTI.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101203
--- Comment #1 from Jonathan Wakely ---
PR 56551 uses a similar idea. It wouldn't be ABI compatible with existing code
though.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101198
--- Comment #2 from Jonathan Wakely ---
I think this will fix it:
--- a/libstdc++-v3/doc/xml/manual/test_policy_data_structures.xml
+++ b/libstdc++-v3/doc/xml/manual/test_policy_data_structures.xml
@@ -105,6 +105,7 @@
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86524
Jonathan Wakely changed:
What|Removed |Added
CC||v at vsamko dot com
--- Comment #13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85319
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Component|libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101211
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101211
--- Comment #2 from Jonathan Wakely ---
Oh, is it this?
unsigned int j:1;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101211
--- Comment #3 from Jonathan Wakely ---
Ah, I bet it started to fail because I added this to the test:
{ dg-add-options no_pch }
So this should fix it for arm:
--- a/libstdc++-v3/testsuite/17_intro/names.cc
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101211
--- Comment #5 from Jonathan Wakely ---
(In reply to Christophe Lyon from comment #4)
> It works for aarch64-linux-gnu, but fails for aarch64-elf (with newlib):
> FAIL: 17_intro/names.cc (test for excess errors)
> Excess errors:
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101213
Jonathan Wakely changed:
What|Removed |Added
Keywords||diagnostic
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92105
--- Comment #7 from Jonathan Wakely ---
Glad we could help ;-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101211
--- Comment #6 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #5)
> (In reply to Christophe Lyon from comment #4)
> > It works for aarch64-linux-gnu, but fails for aarch64-elf (with newlib):
> > FAIL: 17_intro/names.cc (test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97088
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101211
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97088
--- Comment #5 from Jonathan Wakely ---
*** Bug 101211 has been marked as a duplicate of this bug. ***
601 - 700 of 6648 matches
Mail list logo