Re: GCC 9.4 Release Candidate available

On Fri, May 28, 2021 at 7:12 AM Jason Merrill via Gcc wrote: > > On 5/27/21 11:59 PM, Jason Merrill wrote: > > PR100797 seems like a P1 regression from 9.3, I'd like to fix it before > > the release. > > Here's a candidate patch. Going to bed now. I have bootstrapped and tested it on x86_64-unkn

GCC 9.4 Release Candidate Two available

A second release candidate for GCC 9.4 is available from https://sourceware.org/pub/gcc/snapshots/9.4.0-RC-20210528/ and shortly its mirrors. It has been generated from git commit ebfe8b28d40746ff33724bd5b9ade2552e619213, containing a build fix with recent kernel headers and fixes for a few C

Re: GCC Rust git branch

On 28/05/2021 04:05, Thomas Fitzsimmons wrote: > Hi Philip, > > Philip Herron writes: > >> As some of you might know, I have been working on GCC Rust over on >> GitHub https://github.com/Rust-GCC/gccrs. As the project is moving >> forward and enforcing GCC copyright assignments for contributors, I

Re: GCC Rust git branch

On 28/05/2021 04:22, Jason Merrill wrote: > On Mon, May 24, 2021 at 9:25 AM Philip Herron > mailto:philip.her...@embecosm.com>> wrote: > > Hi everyone, > > As some of you might know, I have been working on GCC Rust over on > GitHub https://github.com/Rust-GCC/gccrs >

Re: GCC Rust git branch

On 24/05/2021 19:29, Mark Wielaard wrote: > Hi Philip, > > On Mon, May 24, 2021 at 02:24:13PM +0100, Philip Herron wrote: >> As some of you might know, I have been working on GCC Rust over on >> GitHub https://github.com/Rust-GCC/gccrs. As the project is moving >> forward and enforcing GCC copyrigh

Re: GCC Rust git branch

Philip Herron writes: > On 28/05/2021 04:05, Thomas Fitzsimmons wrote: >> Hi Philip, >> >> Philip Herron writes: >> >>> As some of you might know, I have been working on GCC Rust over on >>> GitHub https://github.com/Rust-GCC/gccrs. As the project is moving >>> forward and enforcing GCC copyrigh

Re: Welcome GCC GSoC 2021 participants

> On 24-May-2021, at 3:12 PM, Martin Jambor wrote: > > Hello, > > On Sun, May 23 2021, Ankur Saini wrote: >> Hello, >> >>> On 18-May-2021, at 9:52 PM, Martin Jambor wrote: >>> >>> All accepted students which do not already have one must request a >>> copyright assignment[1] as soon as poss

Re: C language extension - Automatically cast

* Sławomir Lach: > One of items is automatically cast. For example I declared variable called > Button of GtkButton and pass it to function requires GtkWidget. Why do not > automatically cast to GtkWidget (like in class hierarchy or conversion > operator in C++ or some extra constructors)? But

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

We are porting gcc-10.2.0 to a proprietary OS called VOS with a POSIX API that runs on x86-32. We are using a prior port of gcc-3.4.6 to build the port natively. When the build gets to the point where it compiles libgcc2.c with the gcc-10.2.0 compiler, it goes into an infinite loop and eventuall

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

On Fri, May 28, 2021 at 12:10 PM Barnes, Richard wrote: > > We are porting gcc-10.2.0 to a proprietary OS called VOS with a POSIX API > that runs on x86-32. We are using a prior port of gcc-3.4.6 to build the port > natively. When the build gets to the point where it compiles libgcc2.c with > t

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

Unfortunately, our OS is only a 32-bit OS. It's ABI is only a 32-bit ABI. As you imply, if we had a 64-bit OS, we would have more registers and more memory and would probably avoid this problem. Also, libgcc2.c is supposed to be built natively by the gcc-10.2.0 compiler you have just created. R

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

On Fri, May 28, 2021 at 12:42 PM Barnes, Richard wrote: > > Unfortunately, our OS is only a 32-bit OS. It's ABI is only a 32-bit ABI. As > you imply, if we had a 64-bit OS, we would have more registers and more > memory and would probably avoid this problem. Also, libgcc2.c is supposed to > be

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

Our OS is not built with gcc. It is built with native compilers and linkers. It sounds like you are talking about cross compiling, which is something we have considered but hope to avoid. Richard Barnes From: H.J. Lu Sent: Friday, May 28, 2021 3:52 PM To: Barnes

gcc-10-20210528 is now available

Snapshot gcc-10-20210528 is now available on https://gcc.gnu.org/pub/gcc/snapshots/10-20210528/ 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