Re: Query about compatibility
Chirumamilla Ganesh via Gcc wrote: Does M1 MacBooks support GCC compilers ,if not will M1 MacBooks ever get compatibility of GCC compilers See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96168 and https://github.com/iains/gcc-darwin-arm64 This is experimental at present, support for macOS (Darwin) is a volunteer effort, so time is very imited to work on it. thanks, Iain
Fwd: git commit hook does not record my patches to PRs
Sorry for spamming gcc-patches@ ML, this message should go to gcc@. -- Forwarded message - From: Uros Bizjak Date: Tue, Jan 5, 2021 at 3:04 PM Subject: git commit hook does not record my patches to PRs To: gcc-patc...@gcc.gnu.org Cc: Martin Liska Hello! For some reason git commit hook does not record my patches to PRs, mentioned in the commit message. Some recent examples: PR 98521: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=951bdbde6ade56eb63af1dfa18777348a8a0d89e and PR98522: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=1ff0ddcd8b4728bcc96e1daf2e70a03dc9fbf171 These two patches were committed as a single push (but one commit per push also doesn't reach the PR), and the second one is also missing in the gcc-cvs mailing list archive: https://gcc.gnu.org/pipermail/gcc-cvs/2021-January/date.html In the commit message, I have put PR marks everywhere I can think of, but the commit hook is still ignoring them. Can someone please check, what is wrong with the flow and eventually advise me what to do to enjoy the benefits of the automation. Thanks, Uros.
Re: Copyright assignment for Rust-GCC
On 1/4/21 11:01 PM, Eric Gallager via Gcc wrote: > On Mon, Jan 4, 2021 at 11:13 AM David Edelsohn via Gcc > wrote: > >> On Mon, Jan 4, 2021 at 5:29 AM Nala Ginrut via Gcc >> wrote: >>> Hi Folks! >>> This mail is about the development of Rust frontend of GCC. >>> >>> To avoid misunderstanding, please let me introduce Rust-GCC briefly. >>> In 2013, Philip Herron had announced the project in GCC mailing-list: >>> https://gcc.gnu.org/legacy-ml/gcc/2013-12/msg00017.html >>> In 2019, @SimplyTheOther had contributed the almost complete parser and >>> AST. >>> And I helped to do some trivial work to make it work with the latest GCC >>> at that time. >>> Of course there are more contributors that I can't mention one by one. >>> At that time, a small community of Rust-GCC had formed. We're interested >>> in continuing it till it can be merged into GCC. >>> https://github.com/Rust-GCC/gccrs >>> So this is the brief history. >>> >>> Now we have a question, when should we assign copyright paper for GNU? >>> Last time I assigned the copyright paper, I noticed that the paper >>> mentioned the project name. But Rust-GCC hasn't been recognized by GCC >>> community yet, so I'm not sure if it's the correct time to consider this >>> issue. >>> >>> Comments are welcome. >> As Jeff wrote, the assignment is for the GNU Compiler Collection (GCC) >> project, not for specific languages. One does /not/ submit separate >> assignments for GNU Fortran, GNU C++, GNU Go, GNU Ada, GNU Modula2, >> etc. >> >> > Speaking of Modula2, has that frontend made it into mainline GCC yet? I see > there was a bugzilla component for it added, but I don't remember seeing > anything about it in the changes.html file for any existing releases... No. I haven't seen anyone even trying in a while. jeff
Re: Copyright assignment for Rust-GCC
On Tue, Jan 5, 2021 at 10:48 AM Jeff Law wrote: > > On 1/4/21 11:01 PM, Eric Gallager via Gcc wrote: > > On Mon, Jan 4, 2021 at 11:13 AM David Edelsohn via Gcc > > wrote: > > > >> On Mon, Jan 4, 2021 at 5:29 AM Nala Ginrut via Gcc > >> wrote: > >>> Hi Folks! > >>> This mail is about the development of Rust frontend of GCC. > >>> > >>> To avoid misunderstanding, please let me introduce Rust-GCC briefly. > >>> In 2013, Philip Herron had announced the project in GCC mailing-list: > >>> https://gcc.gnu.org/legacy-ml/gcc/2013-12/msg00017.html > >>> In 2019, @SimplyTheOther had contributed the almost complete parser and > >>> AST. > >>> And I helped to do some trivial work to make it work with the latest GCC > >>> at that time. > >>> Of course there are more contributors that I can't mention one by one. > >>> At that time, a small community of Rust-GCC had formed. We're interested > >>> in continuing it till it can be merged into GCC. > >>> https://github.com/Rust-GCC/gccrs > >>> So this is the brief history. > >>> > >>> Now we have a question, when should we assign copyright paper for GNU? > >>> Last time I assigned the copyright paper, I noticed that the paper > >>> mentioned the project name. But Rust-GCC hasn't been recognized by GCC > >>> community yet, so I'm not sure if it's the correct time to consider this > >>> issue. > >>> > >>> Comments are welcome. > >> As Jeff wrote, the assignment is for the GNU Compiler Collection (GCC) > >> project, not for specific languages. One does /not/ submit separate > >> assignments for GNU Fortran, GNU C++, GNU Go, GNU Ada, GNU Modula2, > >> etc. > >> > >> > > Speaking of Modula2, has that frontend made it into mainline GCC yet? I see > > there was a bugzilla component for it added, but I don't remember seeing > > anything about it in the changes.html file for any existing releases... > No. I haven't seen anyone even trying in a while. Maybe Jeff is not caught up with his email. The GCC SC previously accepted Modula2 support. Richard Biener approved the patch merge a few days ago and Gaius is planning to proceed. Thanks, David
Re: Copyright assignment for Rust-GCC
Thanks for all the replies, I've contacted ass...@gnu.org but no reply for 2 days. Should I get the form from GCC folks? Best regards. Eric Gallager writes: > On Mon, Jan 4, 2021 at 11:13 AM David Edelsohn via Gcc > wrote: > >> On Mon, Jan 4, 2021 at 5:29 AM Nala Ginrut via Gcc >> wrote: >> > >> > Hi Folks! >> > This mail is about the development of Rust frontend of GCC. >> > >> > To avoid misunderstanding, please let me introduce Rust-GCC briefly. >> > In 2013, Philip Herron had announced the project in GCC mailing-list: >> > https://gcc.gnu.org/legacy-ml/gcc/2013-12/msg00017.html >> > In 2019, @SimplyTheOther had contributed the almost complete parser and >> > AST. >> > And I helped to do some trivial work to make it work with the latest GCC >> > at that time. >> > Of course there are more contributors that I can't mention one by one. >> > At that time, a small community of Rust-GCC had formed. We're interested >> > in continuing it till it can be merged into GCC. >> > https://github.com/Rust-GCC/gccrs >> > So this is the brief history. >> > >> > Now we have a question, when should we assign copyright paper for GNU? >> > Last time I assigned the copyright paper, I noticed that the paper >> > mentioned the project name. But Rust-GCC hasn't been recognized by GCC >> > community yet, so I'm not sure if it's the correct time to consider this >> > issue. >> > >> > Comments are welcome. >> >> As Jeff wrote, the assignment is for the GNU Compiler Collection (GCC) >> project, not for specific languages. One does /not/ submit separate >> assignments for GNU Fortran, GNU C++, GNU Go, GNU Ada, GNU Modula2, >> etc. >> >> > Speaking of Modula2, has that frontend made it into mainline GCC yet? I see > there was a bugzilla component for it added, but I don't remember seeing > anything about it in the changes.html file for any existing releases... > > >> Please have all of the developers start the FSF copyright assignment >> process now. >> >> Thanks, David >> -- GNU Powered it GPL Protected it GOD Blessed it HFG - NalaGinrut Fingerprint F53B 4C56 95B5 E4D5 6093 4324 8469 6772 846A 0058 signature.asc Description: PGP signature
Re: Copyright assignment for Rust-GCC
First, please be more patient. People only are now returning from the end of year vacation. And the FSF may not respond immediately in the best of times. Second, you must get the assignment document from the FSF. They create a custom, pre-generated assignment form. It takes time for them to transfer your information to the form and send it. It isn't a click-through CLA. Thanks, David On Tue, Jan 5, 2021 at 11:25 AM Nala Ginrut wrote: > > > Thanks for all the replies, I've contacted ass...@gnu.org but no reply > for 2 days. > Should I get the form from GCC folks? > > Best regards. > > > Eric Gallager writes: > > > On Mon, Jan 4, 2021 at 11:13 AM David Edelsohn via Gcc > > wrote: > > > >> On Mon, Jan 4, 2021 at 5:29 AM Nala Ginrut via Gcc > >> wrote: > >> > > >> > Hi Folks! > >> > This mail is about the development of Rust frontend of GCC. > >> > > >> > To avoid misunderstanding, please let me introduce Rust-GCC briefly. > >> > In 2013, Philip Herron had announced the project in GCC mailing-list: > >> > https://gcc.gnu.org/legacy-ml/gcc/2013-12/msg00017.html > >> > In 2019, @SimplyTheOther had contributed the almost complete parser and > >> > AST. > >> > And I helped to do some trivial work to make it work with the latest GCC > >> > at that time. > >> > Of course there are more contributors that I can't mention one by one. > >> > At that time, a small community of Rust-GCC had formed. We're interested > >> > in continuing it till it can be merged into GCC. > >> > https://github.com/Rust-GCC/gccrs > >> > So this is the brief history. > >> > > >> > Now we have a question, when should we assign copyright paper for GNU? > >> > Last time I assigned the copyright paper, I noticed that the paper > >> > mentioned the project name. But Rust-GCC hasn't been recognized by GCC > >> > community yet, so I'm not sure if it's the correct time to consider this > >> > issue. > >> > > >> > Comments are welcome. > >> > >> As Jeff wrote, the assignment is for the GNU Compiler Collection (GCC) > >> project, not for specific languages. One does /not/ submit separate > >> assignments for GNU Fortran, GNU C++, GNU Go, GNU Ada, GNU Modula2, > >> etc. > >> > >> > > Speaking of Modula2, has that frontend made it into mainline GCC yet? I see > > there was a bugzilla component for it added, but I don't remember seeing > > anything about it in the changes.html file for any existing releases... > > > > > >> Please have all of the developers start the FSF copyright assignment > >> process now. > >> > >> Thanks, David > >> > > > -- > GNU Powered it > GPL Protected it > GOD Blessed it > HFG - NalaGinrut > Fingerprint F53B 4C56 95B5 E4D5 6093 4324 8469 6772 846A 0058
Re: Google GSOC Idea
I wanted to talk about a gcc front-end with the syntax js / ts, which is ahead-of-time. The standard library will also contain basic functions that will enable the use of several basic frameworks that can be used in standard output. It was an e-mail that I could not fully explain because I tried to correct the text a few times, I'm sorry :) We are a group of several people who have already worked on compiler design and we thought of applying this idea under the name gcc. Martin Jambor , 4 Oca 2021 Pzt, 17:37 tarihinde şunu yazdı: > Hi, > > On Sun, Dec 27 2020, Alper G. via Gcc wrote: > > Hello, I am waiting for your suggestions and evaluations about an idea > that > > I am thinking about applying to this year's event of google gsoc. In > short, > > I can say about myself that I am an engineering student and worked on > > compilers as well as several different fields. Nowadays, we see that > > scripting languages such as javascript / typescript are more than just a > > client-side language in the browser. In order to develop applications on > > desktop and mobile devices, there are alternatives such as electron that > > contain chromium and nodejs, have multi-disk-size requirements and cannot > > be packaged statically before runtime, such as react-native. In order to > > overcome such problems, it is necessary to create the ahead-of-time > > compilation, which we are familiar with such as c / c ++, according to > this > > syntax and standards, and to call the graphics libraries and system calls > > directly from within js. Therefore, I want to create a subset of gcc that > > can be statically compiled and contains the ecmascript standards required > > to run common js frameworks native. What are your comments on this > > idea? > > I'm afraid I don't understand it at all. Making GCC "run common js > frameworks" makes very little sense to me. Are you proposing some kind > of JavaScript Front-end (which is not a JIT)? > > > What can we say about the acceptability for gsoc? > > Well, unfortunately I can say only that I do not understand it. If it > is the JavaScript Front-end, the project would too big for a GSoC, by > orders of magnitude, even if severely reduced in scope. > > Martin >
Re: Google GSOC Idea
Are you trying to propose a JavaScript / TypeScript front-end and associated runtime for GCC? I don't believe that anyone would object to that. It probably is much too ambitious for a GSoC project. You could propose a subset as a GSoC project. It's unclear if you already have a preliminary implementation and want to incrementally continue it, like a Hackathon, as part of GSoC. Thanks, David On Tue, Jan 5, 2021 at 2:34 PM Alper G. via Gcc wrote: > > I wanted to talk about a gcc front-end with the syntax js / ts, which is > ahead-of-time. The standard library will also contain basic functions that > will enable the use of several basic frameworks that can be used in > standard output. It was an e-mail that I could not fully explain because I > tried to correct the text a few times, I'm sorry :) We are a group of > several people who have already worked on compiler design and we thought of > applying this idea under the name gcc. > > Martin Jambor , 4 Oca 2021 Pzt, 17:37 tarihinde şunu yazdı: > > > Hi, > > > > On Sun, Dec 27 2020, Alper G. via Gcc wrote: > > > Hello, I am waiting for your suggestions and evaluations about an idea > > that > > > I am thinking about applying to this year's event of google gsoc. In > > short, > > > I can say about myself that I am an engineering student and worked on > > > compilers as well as several different fields. Nowadays, we see that > > > scripting languages such as javascript / typescript are more than just a > > > client-side language in the browser. In order to develop applications on > > > desktop and mobile devices, there are alternatives such as electron that > > > contain chromium and nodejs, have multi-disk-size requirements and cannot > > > be packaged statically before runtime, such as react-native. In order to > > > overcome such problems, it is necessary to create the ahead-of-time > > > compilation, which we are familiar with such as c / c ++, according to > > this > > > syntax and standards, and to call the graphics libraries and system calls > > > directly from within js. Therefore, I want to create a subset of gcc that > > > can be statically compiled and contains the ecmascript standards required > > > to run common js frameworks native. What are your comments on this > > > idea? > > > > I'm afraid I don't understand it at all. Making GCC "run common js > > frameworks" makes very little sense to me. Are you proposing some kind > > of JavaScript Front-end (which is not a JIT)? > > > > > What can we say about the acceptability for gsoc? > > > > Well, unfortunately I can say only that I do not understand it. If it > > is the JavaScript Front-end, the project would too big for a GSoC, by > > orders of magnitude, even if severely reduced in scope. > > > > Martin > >
Re: Google GSOC Idea
We have a pre-implementation trial, although it is not very extensive. We intend to develop this during gsoc and take it forward in a planned manner. David Edelsohn , 5 Oca 2021 Sal, 22:45 tarihinde şunu yazdı: > Are you trying to propose a JavaScript / TypeScript front-end and > associated runtime for GCC? > > I don't believe that anyone would object to that. It probably is much > too ambitious for a GSoC project. You could propose a subset as a > GSoC project. > > It's unclear if you already have a preliminary implementation and want > to incrementally continue it, like a Hackathon, as part of GSoC. > > Thanks, David > > On Tue, Jan 5, 2021 at 2:34 PM Alper G. via Gcc wrote: > > > > I wanted to talk about a gcc front-end with the syntax js / ts, which is > > ahead-of-time. The standard library will also contain basic functions > that > > will enable the use of several basic frameworks that can be used in > > standard output. It was an e-mail that I could not fully explain because > I > > tried to correct the text a few times, I'm sorry :) We are a group of > > several people who have already worked on compiler design and we thought > of > > applying this idea under the name gcc. > > > > Martin Jambor , 4 Oca 2021 Pzt, 17:37 tarihinde şunu > yazdı: > > > > > Hi, > > > > > > On Sun, Dec 27 2020, Alper G. via Gcc wrote: > > > > Hello, I am waiting for your suggestions and evaluations about an > idea > > > that > > > > I am thinking about applying to this year's event of google gsoc. In > > > short, > > > > I can say about myself that I am an engineering student and worked on > > > > compilers as well as several different fields. Nowadays, we see that > > > > scripting languages such as javascript / typescript are more than > just a > > > > client-side language in the browser. In order to develop > applications on > > > > desktop and mobile devices, there are alternatives such as electron > that > > > > contain chromium and nodejs, have multi-disk-size requirements and > cannot > > > > be packaged statically before runtime, such as react-native. In > order to > > > > overcome such problems, it is necessary to create the ahead-of-time > > > > compilation, which we are familiar with such as c / c ++, according > to > > > this > > > > syntax and standards, and to call the graphics libraries and system > calls > > > > directly from within js. Therefore, I want to create a subset of gcc > that > > > > can be statically compiled and contains the ecmascript standards > required > > > > to run common js frameworks native. What are your comments on this > > > > idea? > > > > > > I'm afraid I don't understand it at all. Making GCC "run common js > > > frameworks" makes very little sense to me. Are you proposing some kind > > > of JavaScript Front-end (which is not a JIT)? > > > > > > > What can we say about the acceptability for gsoc? > > > > > > Well, unfortunately I can say only that I do not understand it. If it > > > is the JavaScript Front-end, the project would too big for a GSoC, by > > > orders of magnitude, even if severely reduced in scope. > > > > > > Martin > > > >
Re: gengtype and automatically generated files
On 1/4/21 1:36 PM, Jeff Law wrote: On 1/4/21 10:40 AM, Bill Schmidt via Gcc wrote: Hi! I'm attempting to do something that may not have been done before, so I'm looking for advice, or a pointer to where, in fact, it has been done before. :) I'm automatically generating a back-end header file that declares some structures that include trees, and a bunch of global variables that are also trees. I've marked everything up appropriately, but I also need to teach the garbage collector that this file exists. Most back-end files are automatically scanned by gengtype. Per the documentation, anything that isn't handled automatically needs to be added to target_gtfiles in config.gcc. However, I can't come up with a syntax for describing a file in the gcc/ build subdirectory. Some places in config.gcc allow "./filename" as shorthand for "filename" being in the current build directory, but that doesn't seem to work for adding something to gtyp-input.list. Any recommendations on what I should do next? At the moment it looks like I might have to hack on gengtype to invent a way to scan a file in the build directory, but I have a mild amount of hope that someone has solved this before. Thanks for any help! Yea, I don't see any indication this has ever been done before. I'm a bit surprised that ./ doesn't work since gengtype runs from the build directory and has to reference things in the source directory and ./ would seem to naturally reference the build directory Jeff I've gotten this working, with a little hacking on gengtype needed. I'll propose that patch next stage 1. Bill
