https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61886
--- Comment #32 from rguenther at suse dot de <rguenther at suse dot de> --- On Wed, 11 Feb 2015, hubicka at ucw dot cz wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61886 > > --- Comment #31 from Jan Hubicka <hubicka at ucw dot cz> --- > > So, do we really want to go without this fixed again, for GCC 5? Honza? > > After > > all this is an underlying wrong-code issue! (wrong function is picked as > > prevailing) > > Well, I have only two hands and do not see reasonably simple solution. Will > look into it > again. How this cause wrong code? Hmm, maybe it can't (the "aliases" map to the same symbol). But at least if I produce another decl with say, attribute(regparm), and that gets picked even though I didn't call it then it would be wrong-code (of course that decl is technically invalid as the symbol it refers to has different calling conventions).
