Re: future versions

2015-03-21 Thread Jack Howarth
On Sat, Mar 21, 2015 at 1:45 AM, Markus Trippelsdorf wrote: > On 2015.03.20 at 20:08 -0400, Jack Howarth wrote: >> What was the final decision concerning future versioning of FSF >> gcc post-5.0? In particular, I am confused about the designation of >> maintenance releases of 5.0. Will the nex

Re: future versions

2015-03-21 Thread Markus Trippelsdorf
On 2015.03.21 at 12:11 -0400, Jack Howarth wrote: > On Sat, Mar 21, 2015 at 1:45 AM, Markus Trippelsdorf > wrote: > > On 2015.03.20 at 20:08 -0400, Jack Howarth wrote: > >> What was the final decision concerning future versioning of FSF > >> gcc post-5.0? In particular, I am confused about the

Re: How to implement '@' GDB-like operator for libcc1

2015-03-21 Thread Jan Kratochvil
On Mon, 16 Mar 2015 15:43:21 +0100, Tom Tromey wrote: > It seems like there should be some kind of reference to &op0, that is, > lowering ATSIGN_EXPR to *(typeof(OP0)[OP1]*)(&OP0). OK, I got it now. I was using GDB-like 'struct type *' where 'struct value *' should have been as in GCC both are 't

Re: [gsoc2015] Is Gimple FE eligible for gsoc this year?

2015-03-21 Thread xue yinsong
I add the following code in parser.c to replace htab: … struct gimple_symtab_hasher : ggc_cache_hasher { /* Return the hash value of the declaration name of a gimple_symtab_entry_def object pointed by ENTRY. */ static hashval_t hash(struct gimple_symtab_entry_def *base){return IDENTIFIER_H