On Fri, Jan 29, 2016 at 11:38 AM, Alan Modra wrote:
> Since 4c4a180d, LTO has turned off flag_pic when linking a fixed
> position executable. This results in flag_pic being zero in
> rs6000_file_start, and no definition of ".LCTOC1".
>
> However, when we get to actually
This is the more comprehensive fix for PR68662, the one I'm a little
nervous about applying during stage4. OK for when stage1 opens?
Applying this patch makes
https://gcc.gnu.org/ml/gcc-patches/2016-01/msg02325.html redundant,
but I'm inclined to leave it in: Not initializing the toc symbol at
On Fri, Jan 29, 2016 at 01:20:08PM -0500, David Edelsohn wrote:
> On Fri, Jan 29, 2016 at 11:38 AM, Alan Modra wrote:
> > PR target/68662
> > * config/rs6000/rs6000.c (need_toc_init): New var, set it
> > whenever toc_label_name used.
> >
Since 4c4a180d, LTO has turned off flag_pic when linking a fixed
position executable. This results in flag_pic being zero in
rs6000_file_start, and no definition of ".LCTOC1".
However, when we get to actually emitting code, flag_pic may be on
again, and references made to ".LCTOC1". How
On Fri, Jan 29, 2016 at 11:38 AM, Alan Modra wrote:
> Since 4c4a180d, LTO has turned off flag_pic when linking a fixed
> position executable. This results in flag_pic being zero in
> rs6000_file_start, and no definition of ".LCTOC1".
>
> However, when we get to actually