Re: A value number issue

On Wed, Jul 28, 2021 at 11:03 PM Gary Oblock wrote: > > Richard, > > Here is more on the actual failure. > > From the pre pass dump: > > : > Inserted _975 = (struct node.reorg.reorder *) dedangled_865; > Replaced bea_43->tail with _975 in dedangled_864 = bea_43->tail; > > > > EMERGENCY DUMP: > > v

Re: A value number issue

Richard, I didn't find a use of _975 with that type... A small test case is easier said than done. It's mcf and I pulled a copy out of SPEC for my unit tests (we have a SPEC license) and that passes. However, when I compile it in the SPEC framework, it fails. Otherwise, I'd have used creduce to m

Re: A value number issue

On Thu, Jul 29, 2021 at 9:29 AM Gary Oblock wrote: > > Richard, > > I didn't find a use of _975 with that type... > > A small test case is easier said than done. It's mcf > and I pulled a copy out of SPEC for my unit tests (we have > a SPEC license) and that passes. However, when I compile it > in

Re: How to detect user uses -masm=intel?

* unlvsur unlvsur via Gcc: > What I mean is that what macro GCC sets when it compiles -masm=intel > > > Int main() > { > #ifdef /*__INTEL_ASM*/ > printf(“intel”); > #else > printf(“at&t”); > #endif > } There doesn't seem to be such a macro: $ diff -u <(gcc -dM

Curious Behavior with Fortran gfortran-10.2-catalina.dmg on macOS Big Sur Version 11.4

Dear Sir/Madam: I would firstly like to thank the folks at GCC for their fine work on developing the Fortran compilers, which I have been using for about 12 years now, on a series of four MacBook Pro computers. In total, I have had over 50 years experience using Fortran, this being on a variety

Re: Curious Behavior with Fortran gfortran-10.2-catalina.dmg on macOS Big Sur Version 11.4

On Thu, 29 Jul 2021, 11:59 Lawrence Doctors, wrote: > Dear Sir/Madam: > > I would firstly like to thank the folks at GCC for their fine work on > developing the Fortran compilers, which I have been using for about 12 > years now, on a series of four MacBook Pro computers. In total, I have had > o

Named address spaces on x86 GNU/Linux

The x86-64 architecture supports two instruction prefixes, SEGFS and SEGGS that apply an additional offset to memory operands. The offset lives in a special register that is accessible to the kernel only (historically). On GNU/Linux, SEGFS is used to implement the thread pointer, to avoid dedicat

Re: daily report on extending static analyzer project [GSoC]

I have attached the patches(one is the updated version of previous patch to detect calls via function pointers) of the changed done to make the analyzer understand the calls to virtual functions for initial review. 1. I decided to make a dedicated function to create enodes and eedges for the d

Re: Named address spaces on x86 GNU/Linux

On Thu, 29 Jul 2021, Florian Weimer via Gcc wrote: > On GNU/Linux, SEGFS is used to implement the thread pointer, to avoid > dedicating a general-purpose register to it. At address zero with the > SEGFS prefix, the offset itself is stored so that userspace can read it > without having to call int

Re: rust frontend and UTF-8/unicode processing/properties

For the gcc rust frontend I was thinking of importing a couple of gnulib modules to help with UTF-8 processing, conversion to/from unicode codepoints and determining various properties of those codepoints. But it seems gcc doesn't yet have any gnulib modules imported, and maybe other frontends alr

Re: An asm constraint issue (ARM FPU)

Dear Marc, Sorry for the late answer, I was away for a few days. Yes, that fixes it. THANK YOU! Do you know which gcc source file contains the magic qualifiers for the asm arguments? I wouldn't mind to go through the code and extract what I can. Probably I'd find a couple of gems that are useful

gcc-9-20210729 is now available

Snapshot gcc-9-20210729 is now available on https://gcc.gnu.org/pub/gcc/snapshots/9-20210729/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 9 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: daily report on extending static analyzer project [GSoC]

On Thu, 2021-07-29 at 18:20 +0530, Ankur Saini wrote: > I have attached the patches(one is the updated version of previous > patch to > detect calls via function pointers) of the changed done to make the > analyzer > understand the calls to virtual functions for initial review. > > 1. I decided

RE: How to detect user uses -masm=intel?

Can we add one?? Sent from Mail for Windows 10 From: Florian Weimer Sent: Thursday, July 29, 2021 04:39 To: unlvsur unlvsur via Gcc Cc: Andrew Pinski; unlvsur unlvsur