From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <npickito@gmail.com>
Received: from mail-wm1-x342.google.com (mail-wm1-x342.google.com
 [IPv6:2a00:1450:4864:20::342])
 by sourceware.org (Postfix) with ESMTPS id 3225A3851C3B
 for <binutils@sourceware.org>; Fri,  5 Jun 2020 08:24:29 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3225A3851C3B
Received: by mail-wm1-x342.google.com with SMTP id k26so8204902wmi.4
 for <binutils@sourceware.org>; Fri, 05 Jun 2020 01:24:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=19mtirjRhJIvhk0npc2vWAQjrY6hN+ev+Ndz4Yl65X4=;
 b=AGZPVJHESoqIucbHST/ZqteT4be6na1QvM9XDT+B0tmsrxMvVgC3Rcmq2bO1g/ytTr
 5SIVWSVFMbkLLsyBoYmMbLsJ15Ka4WMgrGxjV/N9ubE5MAoJScWNPMoaE0WvrFzZubbK
 ZlCoX5DasZsNSjAXlWdCfXuZ7KrLAeIIqXxiw/UP9C4vhgkac2ZmsCofoSl05IljoH6Y
 3BtPYnN4vCpbFTpPalR7hbtSG/b/jfpAO8KayrHDDO/DtpdhPJ2ZVNPSQmdl1D07pznA
 qeShtWo7jL5gjUCzVCZq7zvCv9jOkNzL0PoYUIrskW4ue35cc11avbkCjrv4UU/BKaO+
 Qdog==
X-Gm-Message-State: AOAM531JaLJc5iJBS3GXYpKtuvCCI793iHza4bzY2t988Etau6AIc4kl
 /yYySvd0VTzeWKGCDTWwx8YkOepn1bvxyFqjRuY=
X-Google-Smtp-Source: ABdhPJwIzZZyN92pfKX/7pm3JH+o9xVbuBaLKOM3rH82zPSjn5SvgRgygehANPjnbo2Tss3lNWzmtI+0RAnNNCjpGv4=
X-Received: by 2002:a1c:4105:: with SMTP id o5mr1464967wma.168.1591345468145; 
 Fri, 05 Jun 2020 01:24:28 -0700 (PDT)
MIME-Version: 1.0
References: <1590828275-5587-1-git-send-email-nelson.chu@sifive.com>
 <mhng-42715586-6922-4126-8c9c-9921ce2befb5@palmerdabbelt-glaptop1>
 <CAJYME4EjYDGu800GfMiPSZ6do5aGf4vKaJsQq8nheycEPnfxBw@mail.gmail.com>
In-Reply-To: <CAJYME4EjYDGu800GfMiPSZ6do5aGf4vKaJsQq8nheycEPnfxBw@mail.gmail.com>
From: Kito Cheng <kito.cheng@gmail.com>
Date: Fri, 5 Jun 2020 16:24:16 +0800
Message-ID: <CA+yXCZAGa51zhrh5T5QNqHz0mtV08Si8i9LgdOREr9hWUmjZbQ@mail.gmail.com>
Subject: Re: [PATCH 0/2] RISC-V: Fix the conflicting priv spec problems
To: Nelson Chu <nelson.chu@sifive.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>, Binutils <binutils@sourceware.org>
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
 SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: binutils@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Binutils mailing list <binutils.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/binutils>,
 <mailto:binutils-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/binutils/>
List-Post: <mailto:binutils@sourceware.org>
List-Help: <mailto:binutils-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/binutils>,
 <mailto:binutils-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jun 2020 08:24:30 -0000

> -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.