Re: [BUILDROBOT] gcc21 fails to build tilegx-linux

Thanks for the bug report. I have not been able to reproduce the link error in my environment, but I've committed a change to use g++ instead of gcc and I will see if the buildbot does better with that change. The other issues I will fix when gcc is in stage 1. Walter On 2/7/2016 4:10 PM, J

Re: RFC: Update Intel386, x86-64 and IA MCU psABIs for passing/returning empty struct

On Fri, Feb 12, 2016 at 6:58 AM, Matthijs van Duin wrote: > On 11 February 2016 at 16:31, H.J. Lu wrote: >> struct A { >> static void foo (void) (); >> static int xxx; >> }; > > What about it? It's an empty struct. (And it declares a function and > a variable in the namespace of A, which however

Re: gnu-gabi group

On 02/11/2016 06:20 PM, Mark Wielaard wrote: > If we could ask overseers to setup a new group/list gnu-gabi on sourceware > where binutils, gcc, gdb, glibc and other interested parties could join > to maintain these extensions and ask for clarifications that would be > wonderful. I am not a big fa

IPA/cgraph: propagating node frequencies to offloaded functions

Hi! As I'm touching areas of GCC here, that I have no noteworthy experience with (IPA optimizations, cgraph), I'm asking for your help. Thanks! This is primarily to implement a better "avoid offloading" policy for un-parallelized OpenACC kernels constructs with nvptx offloading,

Re: gengtype: conditional GTY ? (to add before GCC 6 release)

On February 12, 2016 3:55:33 PM GMT+01:00, Mikhail Maltsev wrote: > >On 02/12/2016 04:38 PM, Richard Biener wrote: > >> Sorry, no. The plugin API was never considered stable and thus >plugins have to >> deal with incompatibilites as they arise. >> >> Help with picking up the partially completed

Re: RFC: Update Intel386, x86-64 and IA MCU psABIs for passing/returning empty struct

On 11 February 2016 at 16:31, H.J. Lu wrote: > struct A { > static void foo (void) (); > static int xxx; > }; What about it? It's an empty struct. (And it declares a function and a variable in the namespace of A, which however do not have any relevant impact here.) Matthijs van Duin

Re: gengtype: conditional GTY ? (to add before GCC 6 release)

On 02/12/2016 04:38 PM, Richard Biener wrote: > Sorry, no. The plugin API was never considered stable and thus plugins have > to > deal with incompatibilites as they arise. > > Help with picking up the partially completed work on a stable plugin > (introspection) API > is of course welcome. >

Re: gengtype: conditional GTY ? (to add before GCC 6 release)

On 02/12/16 14:38, Richard Biener wrote: On Fri, Feb 12, 2016 at 1:23 PM, Basile Starynkevitch wrote: I am tempted to try implementing a conditional GTY, [...] but this makes sense only if such a gengtype patch would go both into GCC 6 and into the next microrelease of GCC 5, i.e. GCC 5.4 I'

Re: gnu-gabi group

Hi, On Thu, 11 Feb 2016, Mark Wielaard wrote: > If we could ask overseers to setup a new group/list gnu-gabi on > sourceware where binutils, gcc, gdb, glibc and other interested parties > could join to maintain these extensions and ask for clarifications that > would be wonderful. I am not a b

Re: gengtype: conditional GTY ? (to add before GCC 6 release)

On Fri, Feb 12, 2016 at 1:23 PM, Basile Starynkevitch wrote: > Hello All, > > This is motivated by MELT, but I believe it would be useful to every GCC > plugin which tries to be > compilable both for GCC 5 & GCC 6. > > The technical issue described in > https://gcc.gnu.org/ml/gcc/2016-02/msg00149.

gengtype: conditional GTY ? (to add before GCC 6 release)

Hello All, This is motivated by MELT, but I believe it would be useful to every GCC plugin which tries to be compilable both for GCC 5 & GCC 6. The technical issue described in https://gcc.gnu.org/ml/gcc/2016-02/msg00149.html is that the gimple identifier in plugins has changed from pointer

Re: PIE/PIC issue ...w.r.t linker variable

On 12/02/16 09:58, Umesh Kalappa wrote: Hi Kyrill , Thank you for the info ,before i file a bug ,need to confirm its a bug or not . I'm not familiar with linker scripts and the details of -fpie, so unfortunately I can't judge. Do file a bug report. If it is not a bug, it will be closed as suc

Re: PIE/PIC issue ...w.r.t linker variable

Hi Kyrill , Thank you for the info ,before i file a bug ,need to confirm its a bug or not . Thank you ~Umesh On Fri, Feb 12, 2016 at 3:00 PM, Kyrill Tkachov wrote: > Hi, > > > On 12/02/16 09:19, Umesh Kalappa wrote: >> >> Hi Guys , >> >> we do have a issue with below code ,When we enabled the p

Re: PIE/PIC issue ...w.r.t linker variable

Hi, On 12/02/16 09:19, Umesh Kalappa wrote: Hi Guys , we do have a issue with below code ,When we enabled the pie (-fpie/pie) option i.e main.c extern int *my_ptr ; int main() { return *my_ptr; } foo.s .syntax unified .cpu cortex-m0 .fpu softvfp .thumb .global my_ptr

PIE/PIC issue ...w.r.t linker variable

Hi Guys , we do have a issue with below code ,When we enabled the pie (-fpie/pie) option i.e main.c extern int *my_ptr ; int main() { return *my_ptr; } foo.s .syntax unified .cpu cortex-m0 .fpu softvfp .thumb .global my_ptr .global my_var .data .align 2 .type my_pt