Fwd: GCC front end and GCC internals

I am discovering the awesome world of GCC internals. I managed to develop a basic front end. It can call internal and external functions and link with standard libraries. All is good. The hunger for more does not end. I want to call c++ libraries and interact with c++ objects. My starting point w

Re: Fwd: GCC front end and GCC internals

André On Thu, Mar 30, 2017 at 4:03 PM, Martin Jambor wrote: > Hello, > > I am not sure if I can help you but... > > On Thu, Mar 30, 2017 at 08:05:07AM +0200, Andre Groenewald wrote: >> I am discovering the awesome world of GCC internals. I managed to >> develop a basic

Re: Fwd: GCC front end and GCC internals

utomatically add this parameter. I will just use it then. Thanks again for all the help. Regards, André On Fri, Mar 31, 2017 at 10:00 AM, Martin Jambor wrote: > Hi, > > On Fri, Mar 31, 2017 at 08:56:26AM +0200, Andre Groenewald wrote: >> Sorry about the fwd in the de

help with front end and scopes

I am a bit stuck on global, file and local name spaces and scopes. Normally my expression bindings is associated with a function, which makes the function the scope of all the variables. my front end can parse something like this: int testfunc(int parmVar) { int testfuncVar; } int testfunc2(i

Re: help with front end and scopes

classVariable by only submitting testFunc to gimple? Regards, André On Wed, Apr 12, 2017 at 10:36 AM, Richard Biener wrote: > On April 12, 2017 10:24:31 AM GMT+02:00, Andre Groenewald > wrote: >>I am a bit stuck on global, file and local name spaces and scopes. >> >>Normally m

Re: help with front end and scopes

This info is gold. I have much clearer understanding now. Thanks, André On Wed, Apr 12, 2017 at 2:45 PM, Richard Biener wrote: > On Wed, Apr 12, 2017 at 2:07 PM, Andre Groenewald > wrote: >> Thanks for the help. I just want to elaborate just a bit. >> >> So if I under

how to make GCC option hook aware

Hi GCC folks, I have implemented a function for LANG_HOOKS_HANDLE_OPTION for my toy language front end to handle options. The specific option is populated in lang.opt as fdemo-debug My lang-specs file has the following: {"@demo", "demo1 %i %(cc1_options) %{!fsyntax-only:%(invoke_as)}", 0, 1, 0}

Re: how to make GCC option hook aware

I followed your advice and every works great. Thank you, André On Mon, Feb 19, 2018 at 5:25 PM, Michael Matz wrote: > Hi, > > On Sat, 17 Feb 2018, Andre Groenewald wrote: > >> Hi GCC folks, >> >> I have implemented a function for LANG_HOOKS_HANDLE_OPTION for m

Re: GCC contribution

The heart of GCC should remain pure C as far as possible, for the very same reason the Linux kernel is only in C. Deviate from this, and in a few years we will end up with Java as the programming language of GCC. It is the duty of the steering community and our leaders in GCC to be very conservati

Re: GCC contribution

, Mar 30, 2018 at 2:16 PM, Nathan Sidwell wrote: > On 03/29/2018 09:48 AM, Jeff Law wrote: >> >> On 03/29/2018 12:56 AM, Andre Groenewald wrote: > > >>> GCC steering community I count on you and speaking behalf other >>> developers to keep GCC as close to C as