Hi Eric,
> There is an entire machinery in the middle-end and the back-ends to support
> this (look for trampolines/descriptors in the manual and the source code).
> This should essentially work out of the box for any language front-end.
Thanks for the pointer. The documentation I have seen seems
Hello Akshatg,
On Tue, Mar 12 2019, Akshatg wrote:
> Hello all,
>
> I'm a 2nd year Master's student at IIT Bombay. I have taken advance
> compiler related courses in the past semesters. I'm interested to work
> on the project "Make C/C++ not automatically promote
> memory_order_consume to memor
Hello Matias,
On Thu, Mar 14 2019, Matias Barrientos wrote:
> Hello,
>
> I am Matías Barrientos, I am in my third year studying computing
> engineering at the Pontifical University of Valparaiso.
>
> I am very interested in contributing at GCC this year in GSoC. I have
> followed the steps of the
On Wed, Mar 27, 2019 at 8:48 AM Thomas König wrote:
>
> Hi Eric,
> > There is an entire machinery in the middle-end and the back-ends to support
> > this (look for trampolines/descriptors in the manual and the source code).
> > This should essentially work out of the box for any language front-e
On Wed, Mar 27, 2019 at 10:02:21AM +0100, Richard Biener wrote:
> On Wed, Mar 27, 2019 at 8:48 AM Thomas König wrote:
> >
> > Hi Eric,
> > > There is an entire machinery in the middle-end and the back-ends to
> > > support this (look for trampolines/descriptors in the manual and the
> > > source
On Wed, Mar 27, 2019 at 10:09 AM Jakub Jelinek wrote:
>
> On Wed, Mar 27, 2019 at 10:02:21AM +0100, Richard Biener wrote:
> > On Wed, Mar 27, 2019 at 8:48 AM Thomas König wrote:
> > >
> > > Hi Eric,
> > > > There is an entire machinery in the middle-end and the back-ends to
> > > > support this
On 3/25/19 1:36 PM, Moritz Strübe wrote:
> Hi,
>
> I have an issue with the optimization options. We are on an stm32 and it
> only has a prefetcher, but no cache. Thus it's nice to have linear
> default path. For example, we use __builtin_expect in our asserts. Yet
> it seems that this does no
Hey.
Am 25.03.2019 um 13:36 schrieb Moritz Strübe:
> I have the following code:
> --
> #include
> #ifdef UN
> #define UNLIKELY(x) __builtin_expect((x),0)
> #else
> #define UNLIKELY(x) (x)
> #endif
>
> float a = 66;
>
> int test (float b, int test) {
> if(UNLIKELY(test)) {
>
Hi,
On 03/26, Richard Biener wrote:
> On Tue, 26 Mar 2019, David Malcolm wrote:
>
> > On Mon, 2019-03-25 at 19:51 -0400, nick wrote:
> > > Greetings All,
> > >
> > > I would like to take up parallelize compilation using threads or make
> > > c++/c
> > > memory issues not automatically promote.
On 2019-03-27 9:55 a.m., Giuliano Belinassi wrote:
> Hi,
>
> On 03/26, Richard Biener wrote:
>> On Tue, 26 Mar 2019, David Malcolm wrote:
>>
>>> On Mon, 2019-03-25 at 19:51 -0400, nick wrote:
Greetings All,
I would like to take up parallelize compilation using threads or make
>>>
Greetings All,
I've already done most of the work required for signing up for GSoC
as of last year i.e. reading getting started, being signed up legally
for contributions.
My only real concern would be the proposal which I started writing here:
https://docs.google.com/document/d/1BKVeh62IpigsQYf_
Greetings All,
Sorry about another message but seems it was better to write an initial draft
for review here:
https://docs.google.com/document/d/1BKVeh62IpigsQYf_fJqkdu_js0EeGdKtXInkWZ-DtU0/edit
Please let me know what changes or clarity in wording you would like as I'm
assuming
it needs some
On 3/8/19, Joel Sherrill wrote:
> Hi
>
> This may be just an ignorant user question on my part.
>
> Can gcc report when the parameter name in a C prototype
> does not match that used in the implementation?
>
> int f(int x);
>
> int f(int y) {...}
>
> We try to fix every warning gcc reports but thi
13 matches
Mail list logo
