public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bunk at stusta dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/97787] [10/11 regression] 64bit mips lto: .symtab local symbol at index x (>= sh_info of y)
Date: Fri, 13 Nov 2020 19:12:53 +0000	[thread overview]
Message-ID: <bug-97787-4-aFlSovs4LA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97787-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97787

--- Comment #7 from Adrian Bunk <bunk at stusta dot de> ---
(In reply to Richard Biener from comment #6)
> I see.  Still GCC or GAS produces a bogus object file (the original linker
> error).  It might be the new problem is an entirely different one?  It looks
> more and more like a target problem to me.

My guess would be that the situations where -mxgot is required on 64bit MIPS
are not (no longer?) handled properly with LTO.

Note that when compiling from precompiled sources the linker also exits with an
error, the main difference in that case is that the correct "relocation
truncated to fit" error message is not output in the LTO case.

More worrisome is that adding -mxgot to compiler and linker flags did not fix
it in the LTO case.

  parent reply	other threads:[~2020-11-13 19:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 20:09 [Bug lto/97787] New: " bunk at stusta dot de
2020-11-11  7:37 ` [Bug lto/97787] " rguenth at gcc dot gnu.org
2020-11-11  7:39 ` marxin at gcc dot gnu.org
2020-11-11 14:14 ` bunk at stusta dot de
2020-11-11 15:04 ` rguenth at gcc dot gnu.org
2020-11-12 18:52 ` bunk at stusta dot de
2020-11-13  8:35 ` [Bug target/97787] " rguenth at gcc dot gnu.org
2020-11-13 19:12 ` bunk at stusta dot de [this message]
2020-11-16 12:30 ` rguenther at suse dot de
2021-01-16 13:15 ` xry111 at mengyan1223 dot wang
2021-01-16 13:31 ` xry111 at mengyan1223 dot wang
2021-01-16 13:55 ` xry111 at mengyan1223 dot wang
2021-01-16 14:10 ` xry111 at mengyan1223 dot wang
2021-01-18  8:15 ` rguenth at gcc dot gnu.org
2021-01-22 12:04 ` xry111 at mengyan1223 dot wang
2021-01-22 13:19 ` rguenth at gcc dot gnu.org
2021-01-22 16:53 ` xry111 at mengyan1223 dot wang
2021-01-23 12:17 ` xry111 at mengyan1223 dot wang
2021-01-23 13:04 ` xry111 at mengyan1223 dot wang
2021-01-24 12:47 ` xry111 at mengyan1223 dot wang
2021-01-25  8:19 ` rguenth at gcc dot gnu.org
2021-01-25 10:16 ` xry111 at mengyan1223 dot wang
2021-01-25 10:30 ` rguenth at gcc dot gnu.org
2021-01-25 10:49 ` [Bug lto/97787] " pinskia at gcc dot gnu.org
2021-01-25 11:05 ` xry111 at mengyan1223 dot wang
2021-01-25 11:22 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-04-09  7:57 ` rguenth at gcc dot gnu.org
2022-03-22 10:39 ` [Bug lto/97787] [10/11/12 " rguenth at gcc dot gnu.org
2022-03-22 11:19 ` xry111 at mengyan1223 dot wang
2022-03-22 11:33 ` rguenth at gcc dot gnu.org
2022-03-22 11:43 ` jakub at gcc dot gnu.org
2022-06-28 10:42 ` [Bug lto/97787] [10/11/12/13 " jakub at gcc dot gnu.org
2023-07-07 10:38 ` [Bug lto/97787] [11/12/13/14 " rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-97787-4-aFlSovs4LA@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).