From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) by sourceware.org (Postfix) with ESMTPS id CA418388F015 for ; Sat, 14 Aug 2021 22:25:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org CA418388F015 Received: by mail-pj1-x1033.google.com with SMTP id u21-20020a17090a8915b02901782c36f543so26348680pjn.4 for ; Sat, 14 Aug 2021 15:25:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=xYjEYY0agZb3IgYYGWH8SAYiP/Vet96CMM77ivL2BZQ=; b=olZdu/PGgqoOXGrO+4NBolgG7fuWk/rCE7lQznrTal89+mp3b2PQVBcJBOUtF7E7Pd yP1roLM+tKk0xKq0nf1ufDOtkNEOyhFtnLYaXXKn+3nysyKJzACik9/onI5SFePAwOSj OLBXviRKvWwIIGzGHTMp4QdzcDpNspey7scg7rUr3vWR99K9FGXtj66hg9vodFa3Fu1L py41rslWKvMXNjFaba09RPOfp+ikpzyNzEQkRXnrT3vSmjDlmR1FCXUx8CHqcdUyQ0yB WeQZOlGJI3my+FKquQhfnFQDbvQSj7CPIW7ciwbijmIC512YrgGXGoYvCcmo56me/I33 gf1A== X-Gm-Message-State: AOAM532Aantlr53hUIWFvEA/jp2pvD9u2fNjN2FrXW9XjRKcURmna7St vBtZshKVrK2hVbUhRGtzljE= X-Google-Smtp-Source: ABdhPJz7X1PIgVx0K7lKSorXAOlmVANDKoE/CSkUgcB6zgTT0XkcQDOPA5B6AMwZ3bpbe2QCYiZX4A== X-Received: by 2002:a17:90b:3144:: with SMTP id ip4mr8919020pjb.42.1628979907870; Sat, 14 Aug 2021 15:25:07 -0700 (PDT) Received: from localhost (g195.61-45-49.ppp.wakwak.ne.jp. [61.45.49.195]) by smtp.gmail.com with ESMTPSA id nn18sm4810522pjb.21.2021.08.14.15.25.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 14 Aug 2021 15:25:07 -0700 (PDT) Date: Sun, 15 Aug 2021 07:25:05 +0900 From: Stafford Horne To: Giulio Benetti Cc: GCC patches , Richard Henderson , Openrisc Subject: Re: [PATCH v2 0/2] OpenRISC support for cmodel=large Message-ID: References: <20210501211145.2980164-1-shorne@gmail.com> <9e4b2d98-5ba1-c35f-b419-3df2d84a5dab@benettiengineering.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9e4b2d98-5ba1-c35f-b419-3df2d84a5dab@benettiengineering.com> X-Spam-Status: No, score=-4.2 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.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Aug 2021 22:25:19 -0000 On Sun, Aug 15, 2021 at 12:05:37AM +0200, Giulio Benetti wrote: > On 8/15/21 12:03 AM, Stafford Horne wrote: > > On Sat, Aug 14, 2021 at 11:01:16PM +0200, Giulio Benetti wrote: > > > Hi All, > > > > > > On 5/1/21 11:11 PM, Stafford Horne wrote: > > > > Changes from v1: > > > > - Added patch to enabled cmodle=large on crtstuff > > > > > > > > This series fixes some bugs found when linking large binaries, both in buildroot > > > > and glibc testing. > > > > > > > > Stafford Horne (2): > > > > or1k: Add mcmodel option to handle large GOTs > > > > or1k: Use cmodel=large when building crtstuff > > > > > > > > gcc/config/or1k/or1k-opts.h | 30 ++++++++++++++++++++++++++++++ > > > > gcc/config/or1k/or1k.c | 11 +++++++++-- > > > > gcc/config/or1k/or1k.h | 7 +++++++ > > > > gcc/config/or1k/or1k.opt | 19 +++++++++++++++++++ > > > > gcc/doc/invoke.texi | 12 +++++++++++- > > > > libgcc/config.host | 4 ++-- > > > > libgcc/config/or1k/t-crtstuff | 2 ++ > > > > 7 files changed, 80 insertions(+), 5 deletions(-) > > > > create mode 100644 gcc/config/or1k/or1k-opts.h > > > > create mode 100644 libgcc/config/or1k/t-crtstuff > > > > > > > > > > I've tested this patchset and works as expected. > > > It fixed libgeos build failure in conjunction with: > > > https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=3c3de29b048bca6b4aa4235c647b9328e71801b6 > > > > > > Hope this helps to commit it upstream since I still don't see it, or am I > > > wrong? > > > > You are not wrong, I did not push the changed to GCC yet. I will do soon. > > Ah ok, you're the maintainer :-) I thought there was someone else who needed > to push it :-) Yeah, I pushed it now.