[PATCH 0/2] RISC-V: Fix the conflicting priv spec problems

[Kito Cheng]

> -Wl,--link-attrs-mode=[strict? median? loose?]

I would like apply this option on arch string merge too.
but I don't have strong opinion on using same option or separated
option for arch string

> * Strict: the linked objects must have the same privilege version.
> * Median: Allow compatibility, but consider all conflicts  when we
> link objects with different versions of specs.

Median is kind of confusing to me, maybe `compatible`?
and set this as default merge strategy.

> * Loose: Force to link all objects without checking attrs.  Users must
> be responsible when they use this option.

I would prefer using compatible strategy if possible, but discard the
attribute if any conflict for this mode.