https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> --- On Fri, 30 Oct 2015, ranjan.amit8 at gmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028 > > --- Comment #5 from martin <ranjan.amit8 at gmail dot com> --- > Hi Richard, > > There are the changes came after gcc-4.9.3 because of that I am getting above > issue, but if I comment these 2 line in file (tree-streamer-in.c & > tree-streamer-out.c) then it resolves the issue I am facing in gcc-5.2.0. > > Because of these changes, the gcc-5.2.0 fails but gcc-4.9.3 sources are > working fine. > https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=73527b1dbb74fb8a2fcb92627292c1c0334c8364 > > > Index: > =================================================================== > --- a/gcc/tree-streamer-in.c 2015-03-27 12:28:59.000000000 +0530 > +++ b/gcc/tree-streamer-in.c 2015-10-23 03:09:08.758332929 +0530 > @@ -802,7 +802,7 @@ lto_input_ts_function_decl_tree_pointers > /* DECL_STRUCT_FUNCTION is loaded on demand by cgraph_get_body. */ > DECL_FUNCTION_PERSONALITY (expr) = stream_read_tree (ib, data_in); > #ifndef ACCEL_COMPILER > - DECL_FUNCTION_SPECIFIC_TARGET (expr) = stream_read_tree (ib, data_in); > +/* DECL_FUNCTION_SPECIFIC_TARGET (expr) = stream_read_tree (ib, data_in);*/ > #endif > DECL_FUNCTION_SPECIFIC_OPTIMIZATION (expr) = stream_read_tree (ib, > data_in); > > > =================================================================== > --- a/gcc/tree-streamer-out.c 2015-02-26 17:56:11.000000000 +0530 > +++ b/gcc/tree-streamer-out.c 2015-10-23 03:09:13.542332646 +0530 > @@ -708,7 +708,7 @@ write_ts_function_decl_tree_pointers (st > stream_write_tree (ob, DECL_FUNCTION_PERSONALITY (expr), ref_p); > /* Don't stream these when passing things to a different target. */ > if (!lto_stream_offload_p) > - stream_write_tree (ob, DECL_FUNCTION_SPECIFIC_TARGET (expr), ref_p); > + /* stream_write_tree (ob, DECL_FUNCTION_SPECIFIC_TARGET (expr), ref_p);*/ > stream_write_tree (ob, DECL_FUNCTION_SPECIFIC_OPTIMIZATION (expr), ref_p); > } Yes, those are used to implement the feature I was talking about. But the issue lies somewhere in the rs6000 backend and thus needs deeper investigation by one of its maintainers.
