Re: Namespace inside module partition not exported

2021-11-10 Thread Richard Sandiford via Gcc-bugs
Hi, This list is mostly just a bugzilla feed and so isn't widely monitored. If you're confident the behaviour is a bug then it would be better to file a bugzilla ticket. If you're not sure and want to double-check what the correct behaviour is then it'd be better to ask on gcc-help. Thanks,

Re: Compilation of rust-demangle.c fails on MinGW

2021-08-04 Thread Richard Sandiford via Gcc-bugs
Hi, Eli Zaretskii via Gcc-bugs writes: > The version of rust-demangle.c included with Binutils 2.37 doesn't > compile with MinGW: > > mingw32-gcc -c -DHAVE_CONFIG_H -O2 -gdwarf-4 -g3 -I. > -I../../binutils-2.37/libiberty/../include -W -Wall -Wwrite-strings > -Wc++-compat

Re: How GCC treats ice-on-invalid-code?

2020-07-01 Thread Richard Sandiford
Eric Botcazou writes: >> It's fine to file these ice-on-invalid bugs, but don't be surprised if >> nobody has time to work on bugs that are only triggered by unrealistic >> garbage input. > > Right, an ICE is a perfectly valid outcome for garbage input and there are > hundreds of assertions in

Re: How GCC treats ice-on-invalid-code?

2020-06-30 Thread Richard Sandiford
Hi, Haoxin Tu via Gcc-bugs writes: > Hi, there, > > Our team just develop a c++ code generator tool to testing the compiler, > and those days I have reported 13 ICE bugs in ice-on-invalid-bugs. > > Here are the bugs links: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95972 >

Re: [Bug target/92469] ICE: output_operand: invalid use of register 'frame' in 7/8/9/10

2020-05-05 Thread Richard Sandiford
"jakub at gcc dot gnu.org" writes: > --- Comment #9 from Jakub Jelinek --- > Seems neither accessible_reg_set nor operand_reg_set can exclude frame, > because > the latter results in general_operand predicate failing for it and the former > results into the latter not being enabled either. >

Re: [Bug rtl-optimization/91994] [10 Regression] r276327 breaks -mvzeroupper

2019-10-07 Thread Richard Sandiford
"ubizjak at gmail dot com" writes: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91994 > > --- Comment #10 from Uroš Bizjak --- > Richard, since vzeroupper clobbers only xmm0-xmm15 (xmm0-xmm7 on 32it > targets), > shouldn't we use SSE_REGS instead of ALL_SSE_REGS here: > > Index: i386.c >

Re: MIPS: va_arg is unable to correct extract an empty zero-length array

2011-03-20 Thread Richard Sandiford
Nick Clifton ni...@redhat.com writes: Hi Richard, + /* Even zero-sized arguments occupy one byte. */ + if (size == 0) +size = 1; That fixes it! Thanks. Will you apply this patch yourself, or should I submit the patch and the test case as a separate email to gcc-patches ?

Re: MIPS: va_arg is unable to correct extract an empty zero-length array

2011-03-17 Thread Richard Sandiford
Nick Clifton ni...@redhat.com writes: + /* Even zero-sized arguments occupy one byte. */ + if (size == 0) +size = 1; That fixes it! Great! Thanks for confirming. Will you apply this patch yourself, or should I submit the patch and the test case as a separate email to

Re: MIPS: va_arg is unable to correct extract an empty zero-length array

2011-03-15 Thread Richard Sandiford
Nick Clifton ni...@redhat.com writes: Hi Eric, Hi Richard, A customer has reported the following bug with the MIPS target. Since it is for a GNU extension to the C language (zero-length arrays) that is being used in a non-intended fashion (the zero-length array is in a structure

Re: GCC testsuite failures for mips64vrel-elf toolchain with -mlong64 -mgp32

2007-04-04 Thread Richard Sandiford
Nick Clifton [EMAIL PROTECTED] writes: Hi Eric, Hi Richard, I need your brains... The mips64vrel-elf toolchain is showing a lot of unexpected failures in the gcc testsuite (and g++ testsuite) for multilibs which use -mlong64 and -mgp32 together. For example the first one I came

Re: Bug building target libiberty for mips64vrel-elf toolchain

2007-03-29 Thread Richard Sandiford
Hi Eric, Hi Richard, We recently ran across an ICE building a target libiberty for one of the multilibs of the mips64vrel-elf toolchain: .../libiberty/regex.c: In function 'byte_re_match_2_internal': .../libiberty/regex.c:7481: error: insn does not satisfy its constraints:

Re: mips64 - clobberlist errors

2005-01-06 Thread Richard Sandiford
Carl van_Schaik [EMAIL PROTECTED] writes: this becomes a pain since gcc somtimes knows this and uses fp as a gpr, but I cannot clobber it. Why do you want to?