gcc-10-20210604 is now available

2021-06-04 Thread GCC Administrator via Gcc
Snapshot gcc-10-20210604 is now available on https://gcc.gnu.org/pub/gcc/snapshots/10-20210604/ 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

Re: RFC: New mechanism for hard reg operands to inline asm

2021-06-04 Thread Andreas Krebbel via Gcc
On 6/4/21 8:18 PM, Paul Koning wrote: ... > Yes, I would think this should be made a general mechanism that any target > could use. > > I wonder if instead of creating a new mechanism you could do this simply by > creating new constraint names, where each name matches exactly one hard > registe

Re: [EXTERNAL] Re: 64-bit integer typedef's and -fpic lead to infinite loop and growing memory use in port to x86-32

2021-06-04 Thread Barnes, Richard
I found the problem, and it was a mistake I made elsewhere that resulted in %edx being busy everywhere. I have fixed it and consider the issue resolved. Richard Barnes From: Barnes, Richard Sent: Friday, May 28, 2021 3:59 PM To: H.J. Lu Cc: gcc@gcc.gnu.org Sub

Re: RFC: New mechanism for hard reg operands to inline asm

2021-06-04 Thread Paul Koning via Gcc
> On Jun 4, 2021, at 2:02 PM, Andreas Krebbel via Gcc wrote: > > Hi, > > I wonder if we could replace the register asm construct for > inline assemblies with something a bit nicer and more obvious. > E.g. turning this (real world example from IBM Z kernel code): > > int diag8_response(int cm

RFC: New mechanism for hard reg operands to inline asm

2021-06-04 Thread Andreas Krebbel via Gcc
Hi, I wonder if we could replace the register asm construct for inline assemblies with something a bit nicer and more obvious. E.g. turning this (real world example from IBM Z kernel code): int diag8_response(int cmdlen, char *response, int *rlen) { register unsigned long reg2 asm ("2") =

Re: GCC documentation: porting to Sphinx

2021-06-04 Thread Martin Sebor via Gcc
On 6/3/21 4:56 AM, Martin Liška wrote: On 6/2/21 10:41 PM, Martin Sebor wrote: On 5/31/21 7:25 AM, Martin Liška wrote: Hello. I've made quite some progress with the porting of the documentation and I would like to present it to the community now: https://splichal.eu/scripts/sphinx/ Hello.

Re: RFC: Sphinx for GCC documentation

2021-06-04 Thread Koning, Paul via Gcc
> On Jun 4, 2021, at 3:55 AM, Tobias Burnus wrote: > > Hello, > > On 13.05.21 13:45, Martin Liška wrote: >> On 4/1/21 3:30 PM, Martin Liška wrote: >>> That said, I'm asking the GCC community for a green light before I >>> invest >>> more time on it? >> So far, I've received just a small feedba

Re: GCC Rust monthly call

2021-06-04 Thread Philip Herron
Hi everyone, For those interested, you find the meeting notes of our call over on: https://github.com/Rust-GCC/Reporting/blob/main/2021-06-04-community-call.md Thanks, --Phil On Thu, 3 Jun 2021 at 12:33, Philip Herron wrote: > Hi everyone, > > Just a reminder that tomorrow is the community ca

Re: RFC: Sphinx for GCC documentation

2021-06-04 Thread Tobias Burnus
Hello, On 13.05.21 13:45, Martin Liška wrote: On 4/1/21 3:30 PM, Martin Liška wrote: That said, I'm asking the GCC community for a green light before I invest more time on it? So far, I've received just a small feedback about the transition. In most cases positive. [1] https://splichal.eu/scr

Re: GCC documentation: porting to Sphinx

2021-06-04 Thread Martin Liška
On 6/3/21 7:16 PM, Joseph Myers wrote: On Thu, 3 Jun 2021, Martin Liška wrote: On 6/2/21 6:44 PM, Joseph Myers wrote: On Wed, 2 Jun 2021, Joel Sherrill wrote: For RTEMS, we switched from texinfo to Sphinx and the dependency on Python3 for Sphinx has caused a bit of hassle. Is this going to b