public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lancethepants at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/101246] gccgo cross-compiler targeting arm fails to build with gcc 11. Missing structs in runtime.inc. Using uclibc-ng
Date: Thu, 19 Aug 2021 19:36:57 +0000	[thread overview]
Message-ID: <bug-101246-4-nnyOi5hxWv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101246-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Lance Fredrickson <lancethepants at gmail dot com> ---
So I compared runtime.inc in gcc 10.3 and gcc 11.1, and they have quite a bit
different.  I tried using the runtime.inc file from 10.3 in 11.1, and it does
allow it to finish compiling, and I appear to be able to compile a simple go
program.  

I also just removing struct _FILE, which has those to fields __lock and __state
and also completes and I appear to be able to compile some simple go programs.

Not sure if any of this is helpful. I've been trying to figure out all the file
generation is happening, but it's a lot to take in.

  parent reply	other threads:[~2021-08-19 19:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 19:17 [Bug go/101246] New: " lancethepants at gmail dot com
2021-06-28 19:25 ` [Bug go/101246] " ian at airs dot com
2021-06-28 20:36 ` lancethepants at gmail dot com
2021-06-28 20:42 ` ian at airs dot com
2021-06-28 20:48 ` lancethepants at gmail dot com
2021-07-08 21:20 ` lancethepants at gmail dot com
2021-08-19 19:36 ` lancethepants at gmail dot com [this message]
2022-02-23 16:55 ` lancethepants at gmail dot com
2022-03-04 18:47 ` cvs-commit at gcc dot gnu.org
2022-03-04 18:53 ` lancethepants at gmail dot com
2022-03-04 18:56 ` ian at airs dot com

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-101246-4-nnyOi5hxWv@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).