On Wed, Mar 22, 2017 at 11:44:49AM -0600, Kelvin Nilsen wrote: > Internal testing recently revealed that use of the -mno-power9-vector > target option in combination with the -mcpu=power9 target option > results in termination of gcc with the error message: > > power9-dform requires power9-vector
> In both cases, the preferred behavior is that the target option > -mno-power9-vector causes power9-dform to be automatically disabled. > This patch implements the preferred behavior and adds a test case to > demonstrate the fix. Or it could do -mpower9-dform-scalar but disable -mpower9-dform-vector? That seems more reasonable. Ideally none of the -mpower9-dform* or -mpower9-vector options would exist at all, of course. > 2017-03-21 Kelvin Nilsen <kel...@gcc.gnu.org> > > * config/rs6000/rs6000.c (rs6000_option_override_internal): Change > handling of certain combinations of target options, including the > combinations -mpower8-vector vs. -mno-vsx, -mpower8-vector vs. > -mno-power8-vector, and -mpower9_dform vs. -mno-power9-vector. Those other changes are independent? Segher
