Re: -fchecking bug, what does it mean?

[Richard Biener via Gcc]

On Fri, Nov 19, 2021 at 7:35 AM Gary Oblock via Gcc  wrote:
>
> Our test group added "-fchecking" to a script and my optimization
> failed.
>
> I can't find any explanation of this type of bug. I grepped the code
> and flag_checking was all over the place so it's not like
> I can use gdb to pin it down.
>
> Can somebody help me make sense out of this?
>
> lto1: error: type variant differs by TYPE_UNSIGNED
>   size  bitsizetype> constant 64>
> unit-size  sizetype> constant 8>
> align:64 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type 
> 0x7f399333a738 precision:64 min  max 
> 
> pointer_to_this >
>   size  bitsizetype> constant 64>
> unit-size  sizetype> constant 8>
> align:64 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type 
> 0x7f3992d1a3f0 precision:64 min  -9223372036854775808> max 
> pointer_to_this >
> (null):0: confused by earlier errors, bailing out
> lto-wrapper: fatal error: /home/gary/gcc_build_gcc11_v4/install/bin/gcc 
> returned 1 exit status
> compilation terminated.
> [Leaving LTRANS ./exe.lto.o]
> /usr/bin/ld: error: lto-wrapper failed
> [Leaving exe.lto_wrapper_args]
> collect2: error: ld returned 1 exit status
>
> Thanks,
>
> Gary
>
>
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is 
> for the sole use of the intended recipient(s) and contains information that 
> is confidential and proprietary to Ampere Computing or its subsidiaries. It 
> is to be used solely for the purpose of furthering the parties' business 
> relationship. Any unauthorized review, copying, or distribution of this email 
> (or any attachments thereto) is strictly prohibited. If you are not the 
> intended recipient, please contact the sender immediately and permanently 
> delete the original and any copies of this email and any attachments thereto.

Re: How to describe ‘earlyclobber’ explicitly for specific source operand ?

[Peter Bergner via Gcc]

On 11/19/21 1:28 AM, Jojo R via Gcc wrote:
>   We know gcc supply earlyclobber function to avoid register overlap,
> 
>   but it can not describe explicitly for specific source operand, is it 
> right ?

You add the early clobber to the OUTPUT operand(s) that can clobber any of the
input source operands.  You don't mark the source operands that could be 
clobbered.

Peter

gcc-10-20211119 is now available

[GCC Administrator via Gcc]

Snapshot gcc-10-2029 is now available on
  https://gcc.gnu.org/pub/gcc/snapshots/10-2029/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch 
releases/gcc-10 revision 651a542822d4eea7d6328ad365bb45d1d52acc1e

You'll find:

 gcc-10-2029.tar.xz   Complete GCC

  SHA256=33c490e893c32ee81e3a88620ed35cbe786abc07897b4df19a3ea76d0a3b92be
  SHA1=0cdbfea427f001cf940621ac3f64db81569a6d64

Diffs from 10-2022 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-10
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.