From: Sandra Loosemore <sandra@codesourcery.com>
To: Carlos O'Donell <codonell@redhat.com>, Florian Weimer <fw@deneb.enyo.de>
Cc: Joseph Myers <joseph@codesourcery.com>,
Florian Weimer <fweimer@redhat.com>, <libc-alpha@sourceware.org>,
Szabolcs Nagy <szabolcs.nagy@arm.com>, <cltang@codesourcery.com>,
<andrew@codesourcery.com>
Subject: Re: [review v3] slotinfo in struct dtv_slotinfo_list should be flexible array [BZ #25...
Date: Tue, 12 Nov 2019 16:12:14 -0700 [thread overview]
Message-ID: <104ddd32-7fd8-c288-0459-e9450687b562@codesourcery.com> (raw)
In-Reply-To: <320362b6-854f-230e-5db8-af20f66ef838@redhat.com>
On 11/12/19 3:14 PM, Carlos O'Donell wrote:
> If the new glibc cannot be compiled with gcc8 or gcc9 for nios2, then that's
> a problem though. It immediately makes it difficult to test a new glibc on
> existing systems without upgrading the system compiler.
>
> If there is a backend bug then it absolutely needs to be fixed, and it looks
> like Sandra will try that, but that won't reach the affected compilers until
> much much later.
>
> I dislike backing out the changes you made because they are quite nice
> cleanups, and the downstream vendors tend to upgrade glibc and gcc and binutils
> all in one big group to avoid these issues so I don't expect they will ever
> see this problem. It's only us as developers that see the larger version
> skew problem.
IIUC Intel uses whatever versions of binutils/gcc/glibc that Mentor
Graphics gives them (currently 2.32/9.2/2.30 respectively) in their SDK
and does not mess with mainline trunk sources at all. I can raise the
issue with them, but IIRC this would not be the first time some changes
have been made to glibc that require newish tools for building it.
> My inclination is to fix the gcc problem, backport the solution to the active
> FSF branches, and then that fixes our testers.
>
> In order of importance:
> - Fix all gcc10 issues.
> - Fix the nios2 backend issue.
> - Backport nios2 backend to active FSF branches.
> - Rebuild and test to make sure we are all clean again.
Yes, that's my plan.
> How long will that take and is it OK to leave things in a broken state for that long
> for a given target like nios2?
Preparing and testing a patch for the Nios II GCC bug might take a
couple days, but I have another one ahead of it in my queue that I'm
trying to finish before Stage 1 closes at the end of the week. So maybe
a week maximum?
BTW, does this problem affect any other target that tries to use
GP-relative addressing for small data, like MIPS?
-Sandra
next prev parent reply other threads:[~2019-11-12 23:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 17:11 [review] slotinfo in struct dtv_slotinfo_list should be flexible array [BZ #25 Florian Weimer (Code Review)
2019-11-06 16:12 ` Szabolcs Nagy
2019-11-06 16:21 ` Florian Weimer
2019-11-11 15:09 ` Szabolcs Nagy
2019-11-11 15:12 ` Florian Weimer
2019-11-11 21:41 ` Sergio Durigan Junior
2019-11-12 10:22 ` Szabolcs Nagy
2019-11-12 10:35 ` Florian Weimer
2019-11-09 11:44 ` [review v2] " Florian Weimer (Code Review)
2019-11-12 10:40 ` Szabolcs Nagy (Code Review)
2019-11-12 11:47 ` [review v3] " Florian Weimer (Code Review)
2019-11-12 17:29 ` Joseph Myers
2019-11-12 17:42 ` Sandra Loosemore
2019-11-12 18:04 ` Joseph Myers
2019-11-12 18:42 ` Florian Weimer
2019-11-12 20:59 ` Sandra Loosemore
2019-11-13 5:47 ` Florian Weimer
2019-11-13 16:04 ` Sandra Loosemore
2019-11-13 16:25 ` Florian Weimer
2019-11-13 16:06 ` Jeff Law
2019-11-12 22:14 ` Carlos O'Donell
2019-11-12 22:18 ` Florian Weimer
2019-11-12 22:24 ` Carlos O'Donell
2019-11-12 22:26 ` Florian Weimer
2019-11-12 22:39 ` Joseph Myers
2019-11-13 6:18 ` Florian Weimer
2019-11-13 16:05 ` Jeff Law
2019-11-12 23:12 ` Sandra Loosemore [this message]
2019-11-12 23:15 ` Joseph Myers
2019-11-12 12:53 ` Szabolcs Nagy (Code Review)
2019-11-12 13:00 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-12 13:00 ` Sourceware to Gerrit sync (Code Review)
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=104ddd32-7fd8-c288-0459-e9450687b562@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=andrew@codesourcery.com \
--cc=cltang@codesourcery.com \
--cc=codonell@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=szabolcs.nagy@arm.com \
/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).