https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
Richard Biener changed:
What|Removed |Added
Target Milestone|13.2|13.3
--- Comment #17 from Richard Bien
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
Richard Biener changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #18 from Richard B
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
--- Comment #19 from Amyspark ---
Working on it. Is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110315 the patch
you referred to earlier, Richard?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
Amyspark changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.2
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
--- Comment #9 from Amyspark ---
(In reply to Andrew Pinski from comment #7)
> Simple testcase:
> ```
> struct basic_string {
> ~basic_string() { }
> };
> const basic_string data[] = { {} };
> ```
>
> This fails with `ulimit -s 1024` which is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
Christoph Reiter changed:
What|Removed |Added
CC||reiter.christoph at gmail dot
com
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #11 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
Sam James changed:
What|Removed |Added
CC||aldyh at gcc dot gnu.org
See Also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
--- Comment #14 from Sam James ---
(In reply to Alexander Monakov from comment #13)
> The 128KB stack size is for *secondary* threads on musl (i.e. those created
> via pthread_create). The main thread has the same stack as on glibc (GCC
> extend
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
--- Comment #15 from Jakub Jelinek ---
That ICE is because layout_class_type calls c_build_bitfield_integer_type with
width of 0 and that type is then seen by ranger for some reason:
#7 0x00c4eee1 in layout_class_type (t=, virtuals_p=0x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806
--- Comment #16 from Sam James ---
Filed my musl one as PR109868, sorry for clogging up this one!
14 matches
Mail list logo
