From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stefanrin@gmail.com>
Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com
 [IPv6:2607:f8b0:4864:20::102b])
 by sourceware.org (Postfix) with ESMTPS id A17B4385736F
 for <gcc-help@gcc.gnu.org>; Wed,  1 Jun 2022 07:50:09 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A17B4385736F
Received: by mail-pj1-x102b.google.com with SMTP id
 q12-20020a17090a304c00b001e2d4fb0eb4so5388078pjl.4
 for <gcc-help@gcc.gnu.org>; Wed, 01 Jun 2022 00:50:09 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to;
 bh=mGw8SVzGU89tGLQ7PetY5/O87PcpMk0/GkUAYVe5Sfw=;
 b=L7y93DR+wRECJZU6Uo2hexg8vauc8G55ZbsR6Te2DiRQgff1qHeTNDcWUy36aGPL+T
 Q6oCelUCZrQ5HL8e9Ev4oUWUGvnCjTXKQNHRbNZqmIdFSI+yQAwxia3vgVuCSt8+Khq1
 6KdsUHzkSuZqFx9bmLSREUWF+lFEDv1rApiHMYioBhqIpHLxOvdCYzjB9djwYaHiwmsz
 5I0Qfl35AyDsonIudHcGxP2PCvUqv516CHEDeNJySPYC4LdZ8ih8XeMLEF4a4g1V+byI
 6BXysUFNaenU9E8Ho3nfi2jucxzVoZONAgMaTUTW+Y+mu3lz1xH+/fae0Z/66qDbY3A7
 3K5w==
X-Gm-Message-State: AOAM531284U7QHsELNKcgIPudBs5+NG3jTdaCbYwjcSGbuGlsf/4ZCWZ
 NskQmtzzkHBQNUKXZLe7tCRos3I8djvudGiFkAc5qQPg
X-Google-Smtp-Source: ABdhPJwOH8x6c2FZrOsKc9ZTL9fBS6DzbkXST9kH7lg2/G6PBgS2gW3vgKD5BsHwh+frGqwZCD54EkoZhNjKIflAC3k=
X-Received: by 2002:a17:902:8ecb:b0:162:bc8:9361 with SMTP id
 x11-20020a1709028ecb00b001620bc89361mr52604118plo.25.1654069808560; Wed, 01
 Jun 2022 00:50:08 -0700 (PDT)
MIME-Version: 1.0
References: <DM6PR05MB4697943468A2831347EA3781D6DC9@DM6PR05MB4697.namprd05.prod.outlook.com>
In-Reply-To: <DM6PR05MB4697943468A2831347EA3781D6DC9@DM6PR05MB4697.namprd05.prod.outlook.com>
From: Stefan Ring <stefanrin@gmail.com>
Date: Wed, 1 Jun 2022 09:49:57 +0200
Message-ID: <CAAxjCEyb=nqyeGUXK7kxxMdgyAFio5ztZ_Grj6Pr=7qkVjgkUw@mail.gmail.com>
Subject: Re: x86_64 windows binaries are always PIC?
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-0.6 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,
 T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: gcc-help@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-help mailing list <gcc-help.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-help>,
 <mailto:gcc-help-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-help>,
 <mailto:gcc-help-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2022 07:50:11 -0000

On Tue, May 31, 2022 at 9:49 PM unlvsur unlvsur via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> I found that GCC would always use %rip as the reference for the symbols for x86_64 windows binaries. Is it mandatory by windows and impossible to disable it?

I guess because almost all addressing modes work only with 32-bit
immediates, so there is no way to represent absolute memory addresses
in machine code.