From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-195138-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 37750 invoked by alias); 31 Jan 2018 15:56:42 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 37739 invoked by uid 89); 31 Jan 2018 15:56:42 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*i:sk:XPXw@ma, H*f:sk:XPXw@ma
X-HELO: mail-oi0-f43.google.com
Received: from mail-oi0-f43.google.com (HELO mail-oi0-f43.google.com) (209.85.218.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 31 Jan 2018 15:56:41 +0000
Received: by mail-oi0-f43.google.com with SMTP id b3so7983181oib.11        for <gcc@gcc.gnu.org>; Wed, 31 Jan 2018 07:56:40 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20161025;        h=x-gm-message-state:mime-version:in-reply-to:references:from:date         :message-id:subject:to:cc;        bh=MpzVifcbTQkvUMwh7vAmlnRVJfC/0JDan+lBxcT9j30=;        b=SwPRxrOFQ/1EsaVW/jmxDwRZ2jrEyKr0Ri7z2nRurxnwlcZHFS3hLZ0/0/HKvsLMOG         sIapwX1J4YsxLR+oUU+Q7mDeWBinJXjfgF80i8fUjJwaqU/cUjdfH/JFvi0FIwm/XhsJ         nY5au0y6iAQ6g7wsEhEW513c8VlIaqabxTcSDyPDWtYKngAUckJEnPSkc1h3F7LadMCV         zXzpo2IQDg2tj6NCDgp82gD3zxEWYcoyJ5EJn/KwnFtzzyWNIeej0ahkzKeorCkcfQ/3         2RrJ1MtwsNNxenkXQ8ivnRGqoSzmEnjUGMgY4e7L495N079FtzhHYDLwjh7n+eQG206g         Wmsg==
X-Gm-Message-State: AKwxytdhPySTOh9gLmZkJ/BgY0ArEvFwhrdLBicjmzKJYwX10pvM9VPp	eJrDXDSEUDiofQ1nc4hQcD7zyZ3zahOUXSUiUuI=
X-Google-Smtp-Source: AH8x2251llQVmTGuIEuIQaGpNiAWc74TdZ6STf4+17BEKgDXWRfjLIsNzwiZYd86EES+zoJt2NNddMLPEJbrWSBoe28=
X-Received: by 10.202.49.136 with SMTP id x130mr11077954oix.34.1517414199224; Wed, 31 Jan 2018 07:56:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.177.2 with HTTP; Wed, 31 Jan 2018 07:56:38 -0800 (PST)
In-Reply-To: <CAApLimjbutLH30Pp17DT1UkBxsJebx0zRnFRTnyJ6Bbuf=XPXw@mail.gmail.com>
References: <CAApLimiqPc0BFqy28jDQXJH-A_cMzuJ9yD=ceeFM=gP0wnrysQ@mail.gmail.com> <CAMe9rOoB8k49qFW91mBOysjJ2XfvaYV4xLxVtv78CKZGAeptiQ@mail.gmail.com> <CAApLimjeW5i1NcrU5BS6v7Jv8tbV9VAaxOQ_FBG6TSBG6Na19Q@mail.gmail.com> <CAMe9rOqMFyoq9iW_fim_uJbUtmMq5tFcFVdo7Q+QSaa8Gc6zFg@mail.gmail.com> <CAApLimjwGk8fH21cGk1acg3N7ewc=n-82_Xm7iff0yKmt3+93w@mail.gmail.com> <CAMe9rOraUoMn2Wv0HN1+uDZjDZYoLgpsjOZkEX3+MQmJ8SnFMA@mail.gmail.com> <CAApLimjbutLH30Pp17DT1UkBxsJebx0zRnFRTnyJ6Bbuf=XPXw@mail.gmail.com>
From: "H.J. Lu" <hjl.tools@gmail.com>
Date: Wed, 31 Jan 2018 15:56:00 -0000
Message-ID: <CAMe9rOr59CxcgL5-n3jENmtB-HoyqXLXjy9qQJ3zqSg-H1-HNg@mail.gmail.com>
Subject: Re: -static-pie and -static -pie
To: lists@coryfields.com
Cc: GCC Development <gcc@gcc.gnu.org>
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2018-01/txt/msg00260.txt.bz2

On Wed, Jan 31, 2018 at 7:44 AM, Cory Fields <lists@coryfields.com> wrote:
> After looking at this for quite a while, I'm afraid I'm unsure how to proceed.
>
> As of now, static and static-pie are mutually exclusive. So given the
> GNU_USER_TARGET_STARTFILE_SPEC you pasted
> earlier, "static" matches before "static-pie", causing the wrong start files.
>
> It seems to me that the static-pie target complicates things more than
> matching against static+pie individually.
>
> If I convert -static + -pie to -static-pie, then "static" won't be
> matched in specs, where maybe it otherwise should. Same for -pie.
>
> Would you prefer to swallow -static and -pie and pass along only
> -static-pie? Or forward them all along, and fix the specs which look

Yes.  When you see both -static and -pie. regardless of their relative
order on command-line, you

1. Remove -static and -pie.
2. Add -static-pie.

> for static before static-pie ?
>



-- 
H.J.