[Bug fortran/97864] Homebrew Operator Overload ICE

2020-11-25 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97864 Iain Sandoe changed: What|Removed |Added Status|NEW |RESOLVED Target Milestone|---

[Bug target/97865] libtool needs to be updated for Darwin20.

2020-11-25 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 Iain Sandoe changed: What|Removed |Added Target Milestone|--- |8.5 --- Comment #25 from Iain Sandoe ---

[Bug fortran/97864] Homebrew Operator Overload ICE

2020-11-25 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97864 --- Comment #14 from Iain Sandoe --- (In reply to Francois-Xavier Coudert from comment #13) > And the backtrace is identical, too. It's a duplicated of > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768 OK - so I imagine Jakub will back port

[Bug fortran/97864] Homebrew Operator Overload ICE

2020-11-25 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97864 --- Comment #11 from Iain Sandoe --- do you see this on mainline too? (I do not - but building a 10.x debug compiler at present) -- the trick will be to figure out what fortran patch(es) have apparently fixed this on mainline. There doesn't

[Bug fortran/97864] Homebrew Operator Overload ICE

2020-11-25 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97864 --- Comment #9 from Iain Sandoe --- I would not expect anything to have changed with 10.2 (it's a released version) unless Homebrew were to back port something. Are you able to test with 'master' (i.e. the development version for GCC-11)?

[Bug fortran/97864] Homebrew Operator Overload ICE

2020-11-25 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97864 --- Comment #7 from Iain Sandoe --- (In reply to Brad Richardson from comment #6) > I recently updated to Big Sur, and have xcode version 12.2, but this > initially occurred on Catalina. I don't know exactly which version of xcode > was

[Bug target/97865] libtool needs to be updated for Darwin20.

2020-11-19 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 --- Comment #24 from Iain Sandoe --- (In reply to Iain Sandoe from comment #22) > (In reply to Iain Sandoe from comment #19) > > (In reply to Jürgen Reuter from comment #16) > > > (In reply to Iain Sandoe from comment #15) > > > > (In reply to

[Bug fortran/97864] Homebrew Operator Overload ICE

2020-11-19 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97864 Iain Sandoe changed: What|Removed |Added CC||iains at gcc dot gnu.org --- Comment #5

[Bug target/97865] libtool needs to be updated for Darwin20.

2020-11-19 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 --- Comment #22 from Iain Sandoe --- (In reply to Iain Sandoe from comment #19) > (In reply to Jürgen Reuter from comment #16) > > (In reply to Iain Sandoe from comment #15) > > > (In reply to Jürgen Reuter from comment #14) > > > > clang:

[Bug target/97865] libtool needs to be updated for Darwin20.

2020-11-19 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 --- Comment #21 from Iain Sandoe --- (In reply to Jürgen Reuter from comment #16) > (In reply to Iain Sandoe from comment #15) > > (In reply to Jürgen Reuter from comment #14) > (4) I checked that on my system there is an older version of

[Bug target/97865] libtool needs to be updated for Darwin20.

2020-11-19 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 --- Comment #20 from Iain Sandoe --- (In reply to Jürgen Reuter from comment #16) > (In reply to Iain Sandoe from comment #15) > > (In reply to Jürgen Reuter from comment #14) > - #if defined( AIX_PHYSADR_T_CHECK ) > - typedef struct

[Bug target/97865] libtool needs to be updated for Darwin20.

2020-11-19 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 --- Comment #19 from Iain Sandoe --- (In reply to Jürgen Reuter from comment #16) > (In reply to Iain Sandoe from comment #15) > > (In reply to Jürgen Reuter from comment #14) > clang: error: argument unused during compilation: '-no-pie' >

[Bug target/97865] libtool needs to be updated for Darwin20.

2020-11-19 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 --- Comment #18 from Iain Sandoe --- (In reply to Jürgen Reuter from comment #17) > Iain, as I wrote below your changes seem not sufficient, I will recheck when > I build your branch with gmp/mpfr/mpc built with dynamic_lookup, but it > seems

[Bug target/97865] libtool needs to be updated for Darwin20.

2020-11-18 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 --- Comment #15 from Iain Sandoe --- (In reply to Jürgen Reuter from comment #14) > If there is a git branch or so, I could also test it on my system with our > code whether this works as expected. Here you go - this is config.{sub, guess},

[Bug target/97865] libtool needs to be updated for Darwin20.

2020-11-17 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 --- Comment #13 from Iain Sandoe --- (In reply to jos...@codesourcery.com from comment #12) > config.sub and config.guess are imported, unmodified, from upstream > config.git. thanks I will try to do that and test it over the next days (I've

[Bug target/97865] MACOSX_DEPLOY_TARGET needs to be updated

2020-11-17 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 --- Comment #11 from Iain Sandoe --- Created attachment 49581 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49581=edit regenerated files the second patch is all the regenerated files .. much larger :)

[Bug target/97865] MACOSX_DEPLOY_TARGET needs to be updated

2020-11-17 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 Iain Sandoe changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned at

[Bug c++/97871] [11 Regression] ICE in cp_parser_declaration, at cp/parser.c:13539

2020-11-17 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97871 Iain Sandoe changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/97871] [11 Regression] ICE in cp_parser_declaration, at cp/parser.c:13539

2020-11-17 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97871 --- Comment #2 from Iain Sandoe --- (In reply to Marek Polacek from comment #1) > Started with r11-4927. Iain, I think the assert should go: > > --- a/gcc/cp/parser.c > +++ b/gcc/cp/parser.c > @@ -13536,7 +13536,6 @@ cp_parser_declaration

[Bug target/97865] MACOSX_DEPLOY_TARGET needs to be updated

2020-11-17 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 --- Comment #8 from Iain Sandoe --- (In reply to Jürgen Reuter from comment #4) > (In reply to Iain Sandoe from comment #3) > > I didn't have x86 Big Sur until the weekend - still working through things. > > 1/ > > > > The change you have

[Bug target/97865] MACOSX_DEPLOY_TARGET needs to be updated

2020-11-17 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 --- Comment #7 from Iain Sandoe --- (In reply to Jürgen Reuter from comment #6) > (In reply to Iain Sandoe from comment #5) > > I bootstrapped several times (without using MACOSX_DEPLOYMENT_TARGET) and > > have been looking into other issues. >

[Bug target/97865] MACOSX_DEPLOY_TARGET needs to be updated

2020-11-17 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 --- Comment #5 from Iain Sandoe --- I bootstrapped several times (without using MACOSX_DEPLOYMENT_TARGET) and have been looking into other issues. Note that the libgfortran directory throws up a lot of warnings when 'autoreconf'ed' so maybe

[Bug target/97865] MACOSX_DEPLOY_TARGET needs to be updated

2020-11-17 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97865 Iain Sandoe changed: What|Removed |Added Last reconfirmed||2020-11-17 Ever confirmed|0

[Bug c++/87403] [Meta-bug] Issues that suggest a new warning

2020-11-13 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87403 Bug 87403 depends on bug 77404, which changed state. Bug 77404 Summary: Add Wobjc-root-class https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77404 What|Removed |Added

[Bug objc/77404] Add Wobjc-root-class

2020-11-13 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77404 --- Comment #9 from Iain Sandoe --- fixed for GCC-11

[Bug objc/77404] Add Wobjc-root-class

2020-11-13 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77404 Iain Sandoe changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug sanitizer/95137] Sanitizers seem to be missing support for coroutines

2020-11-12 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95137 --- Comment #37 from Iain Sandoe --- (In reply to Avi Kivity from comment #36) > A reminder that coroutines are crippled without this fixed, as it is > standard practice these days to use sanitizers. Although I have taken the PR, please don't

[Bug objc/77404] Add Wobjc-root-class

2020-11-12 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77404 Iain Sandoe changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |iains at gcc dot gnu.org Target

[Bug tree-optimization/97757] [11 Regression] fortran save_6.f90 fails with a segv for -flto -O >= 2

2020-11-08 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97757 Iain Sandoe changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug tree-optimization/97757] New: [11 Regression] fortran save_6.f90 fails with a segv for -flto -O >= 2

2020-11-08 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97757 Bug ID: 97757 Summary: [11 Regression] fortran save_6.f90 fails with a segv for -flto -O >= 2 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug testsuite/97680] [11 Regression] new test case c-c++-common/zero-scratch-regs-10.c in r11-4578 has excess errors

2020-11-08 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97680 --- Comment #6 from Iain Sandoe --- (In reply to Iain Sandoe from comment #5) > I added xfail-if for powerpc-darwin (8,9, 10 and 11). > > https://gcc.gnu.org/pipermail/gcc-cvs/2020-November/336720.html > > Since i don't think I will have time

[Bug c/78352] GCC lacks support for the Apple "blocks" extension to the C family of languages

2020-11-08 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78352 --- Comment #15 from Iain Sandoe --- (In reply to Fabian Groffen from comment #14) > (In reply to Eric Gallager from comment #13) > > If we could get in touch with an actual lawyer to review which laws > > specifically are getting in the way

[Bug testsuite/97680] [11 Regression] new test case c-c++-common/zero-scratch-regs-10.c in r11-4578 has excess errors

2020-11-07 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97680 --- Comment #5 from Iain Sandoe --- I added xfail-if for powerpc-darwin (8,9, 10 and 11). https://gcc.gnu.org/pipermail/gcc-cvs/2020-November/336720.html Since i don't think I will have time this cycle to implement it (there are much more

[Bug c/78352] GCC lacks support for the Apple "blocks" extension to the C family of languages

2020-11-07 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78352 --- Comment #12 from Iain Sandoe --- (In reply to Fabian Groffen from comment #11) > Is there a patch or WIP somewhere I can try out or attempt to bring forwards? I need to bring forward my patches to the latest master, will post a link here

[Bug tree-optimization/97666] [11 Regression] bootstrap fail for powerpc-darwin while building libgfortran after r11-4485

2020-11-01 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97666 Iain Sandoe changed: What|Removed |Added Keywords||ice-on-valid-code Target|

[Bug tree-optimization/97666] New: [11 Regression] bootstrap fail for powerpc-darwin while building libgfortran after r11-4485

2020-11-01 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97666 Bug ID: 97666 Summary: [11 Regression] bootstrap fail for powerpc-darwin while building libgfortran after r11-4485 Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug c++/96504] [coroutines] Use after free in std::__n4861::coroutine_handle::done()

2020-11-01 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96504 --- Comment #5 from Iain Sandoe --- (In reply to H.J. Lu from comment #4) > __builtin_coro_resume and __builtin_coro_destroy delete the memory. > Everything goes downhill after it. thanks for the analysis - I will hopefully take a look later.

[Bug c++/95519] [coroutines] non-functions for promise_type::return_void not supported

2020-10-31 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95519 --- Comment #10 from Iain Sandoe --- (In reply to H.J. Lu from comment #9) > On AVX or AVX512 machines, I got (I test on AVX and AVX512 machines without seeing this) What version of glibc do you have? this might be a dup of PR96504 (r11-1673

[Bug c++/97452] [coroutines] incorrect sequencing of await_resume() when multiple co_await expressions occur in a single statement

2020-10-29 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97452 --- Comment #5 from Iain Sandoe --- (In reply to David Ledger from comment #4) > @Iain Sandoe > In terms of the standard do you think this is technically undefined > behaviour? no, AFAICT, it's just a regular bug in the implementation. (it's

[Bug c++/97438] [accepts-invalid] coroutines accepts prmomise type with both return_value() and return_void()

2020-10-19 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97438 Iain Sandoe changed: What|Removed |Added Resolution|--- |FIXED Last reconfirmed|

[Bug c++/97452] [coroutines] incorrect sequencing of await_resume() when multiple co_await expressions occur in a single statement

2020-10-17 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97452 --- Comment #3 from Iain Sandoe --- (In reply to David Ledger from comment #2) > I'm happy to use this thread for the issue, I can just repost my link to the > same issue here. > > My reporting of the issue is here, but Lewis Bakers example is

[Bug c++/97452] [coroutines] incorrect sequencing of await_resume() when multiple co_await expressions occur in a single statement

2020-10-16 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97452 --- Comment #1 from Iain Sandoe --- probably a dup of 97433.

[Bug c++/97433] C++20 Coroutines, Unexpected reordering of await_resume, return_value and yield_value

2020-10-16 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97433 Iain Sandoe changed: What|Removed |Added Last reconfirmed||2020-10-16 Assignee|unassigned

[Bug c++/97452] [coroutines] incorrect sequencing of await_resume() when multiple co_await expressions occur in a single statement

2020-10-16 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97452 Iain Sandoe changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug bootstrap/92719] MacOS 10.15 Catalina build fails

2020-10-13 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92719 --- Comment #6 from Iain Sandoe --- (In reply to Nikhil Benesch from comment #5) > Ah, sorry, I was imprecise before. By “system gmp” I meant a gmp installed > by Homebrew, as in `brew install gmp`. So ... I am guessing that the default

[Bug bootstrap/92719] MacOS 10.15 Catalina build fails

2020-10-02 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92719 --- Comment #4 from Iain Sandoe --- (In reply to Nikhil Benesch from comment #3) > For posterity, I could reproduce this issue even with the suggested > `./configure` arguments, i.e., excluding the `--enable-multilib` option. > I worked around

[Bug target/96968] aarch64 : ICE in vregs or expand pass, lowering __builtin_aarch64_get_{fpcr,fpsr,fpcr64,fpsr64}

2020-09-29 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96968 --- Comment #9 from Iain Sandoe --- (In reply to Andrea Corallo from comment #8) > "iains at gcc dot gnu.org via Gcc-bugs" writes: > [...] > > unfortunately, I've not been able to test since you applied this - currently &

[Bug ipa/97244] [11 Regression] ICE in ipa_edge_args_sum_t::duplicate at gcc/ipa-prop.c:4251 since r11-3478-gada353b87909fd6c

2020-09-29 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97244 Iain Sandoe changed: What|Removed |Added CC||iains at gcc dot gnu.org --- Comment #1

[Bug libbacktrace/97082] new test 'mtest' fails for Mach-O/Darwin.

2020-09-29 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97082 --- Comment #3 from Iain Sandoe --- (In reply to Ian Lance Taylor from comment #2) > Does btest pass? It's hard to see why mtest would fail if btest passes. current results [darwin16, darwin19] are: PASS: allocfail.sh PASS: test_elf_32 PASS:

[Bug target/96968] aarch64 : ICE in vregs or expand pass, lowering __builtin_aarch64_get_{fpcr,fpsr,fpcr64,fpsr64}

2020-09-24 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96968 --- Comment #7 from Iain Sandoe --- (In reply to Andrea Corallo from comment #6) > I believe f5e73de00e9c853ce65333efada7409b0d00f758 should have fixed > this. > > Okay to close? unfortunately, I've not been able to test since you applied this

<    5   6   7   8   9   10