On Wed, Sep 30, 2020 at 01:39:11PM +0200, Jakub Jelinek wrote: > On Wed, Sep 30, 2020 at 01:21:44PM +0200, Stefan Schulze Frielinghaus wrote: > > I think the problem boils down that on S/390 we distinguish between four > > states of a flag: explicitely set to yes/no and implicitely set to > > yes/no. If set explicitely, the option wins. For example, the options > > `-march=z10 -mhtm` should enable the hardware transactional memory > > option although z10 does not have one. In the past if a flag was set or > > not explicitely was encoded into opts_set->x_target_flags ... for each > > flag individually, e.g. TARGET_OPT_HTM_P (opts_set->x_target_flags) was > > Oops, seems I've missed that set_option has special treatment for > CLVC_BIT_CLEAR/CLVC_BIT_SET. > Which means I'll need to change the generic handling, so that for > global_options_set elements mentioned in CLVC_BIT_* options are treated > differently, instead of using the accumulated bitmasks they'll need to use > their specific bitmask variables during the option saving/restoring. > Is it ok if I defer it for tomorrow? Need to prepare for OpenMP meeting now.
Sure, no problem at all. In that case I stop to investigate further and wait for you. Cheers, Stefan
