Re: End of subscription

2023-05-23 Thread LIU Hao via Gcc
在 2023/5/19 20:59, Florian Weimer via Gcc 写道: * Jonathan Wakely via Gcc: Unfortunately even the Gmail web UI doesn't offer an unsubscribe option, despite knowing the mails come from a list and showing: mailing list: gcc@gcc.gnu.org Filter messages from this mailing list It does for me, under

Re: gcc-12.3 cannot build gcc-ada on Cygwin

2023-05-23 Thread LIU Hao via Gcc
在 2023/5/23 04:08, Achim Gratz 写道: I've backported the patch _and_ defined both WIN32_LEAN_AND_MEAN and COM_NO_WINDOWS_H (of which I find no reference anywhere in the sources, so it's probably doing something in the Windows headers?) and the build has been working through stage 3. That look lik

Wrong cost computation / conclusion ins insn combine?

2023-05-23 Thread Georg-Johann Lay
For some time now I am staring at the following test case and what combine does with it: typedef struct { unsigned b0 : 1; unsigned b1 : 1; unsigned b2 : 1; unsigned b3 : 1; unsigned b4 : 1; unsigned b5 : 1; unsigned b6 : 1; unsigned b7 : 1; } b_t; Prior to combin

Re: Differences between clang and gcc handling of int[static n] function arguments

2023-05-23 Thread Jonathan Wakely via Gcc
On Mon, 22 May 2023, 00:40 peter0x44 via Gcc, wrote: > > I would be happy to open a PR to improve this warning, if there isn't > one already. > Please do. > > It seems it might even be trivial enough for me to investigate and > tackle myself, in some spare time. > > I see very little code usin

Re: RISC-V GCC Patchwork Sync-Up Meeting

2023-05-23 Thread Palmer Dabbelt
On Tue, 18 Apr 2023 08:34:34 PDT (-0700), Palmer Dabbelt wrote: On Mon, 17 Apr 2023 08:08:42 PDT (-0700), Palmer Dabbelt wrote: The topic of having some sort of RISC-V development meeting has come up a handful of times, but we never got around to actually setting anything up. We've had a patchw

[patch]: Implement PR104327 for avr

2023-05-23 Thread Georg-Johann Lay
PR target/104327 not only affects s390 but also avr: The avr backend pre-sets some options depending on optimization level. The inliner then thinks that always_inline functions are not eligible for inlining and terminates with an error. Proposing the following patch that implements TARGET_CAN_INL

inlining failed in call to 'always_inline': target specific option mismatch

2023-05-23 Thread Georg-Johann Lay
This error pops up in the testsuite for avr. As far as I understand, this is due to target-specific optimization like in avr-common.cc: { OPT_LEVELS_1_PLUS_NOT_DEBUG, OPT_mgas_isr_prologues, NULL, 1 }, { OPT_LEVELS_1_PLUS, OPT_mmain_is_OS_task, NULL, 1 }, // Stick to the "old" plac