From: Stafford Horne <shorne@gmail.com>
To: GLIBC patches <libc-alpha@sourceware.org>
Subject: Upstreaming OpenRISC with GCC mainline
Date: Thu, 28 Oct 2021 05:49:13 +0900 [thread overview]
Message-ID: <CAAfxs77MfWtYGYLgycvF0Utvq-rqbfaekCHAWL5R2bDLa3oKKQ@mail.gmail.com> (raw)
Hello,
I currently am working through some of the final TODO items from
NewPorts[0] for upstreaming the OpenRISC GLIBC port I have been
working on.
- make check - DONE 1 failure (tst-tzset fails to create 4GB file, my
tmp space is not big enough)
- merged, split, cleaned up patches - DONE
- build-many-glibcs.py - FAILS, GCC mainline warnings
Up until now I have been maintaining a patch[1] for fixing various GCC
mainline related issues to keep things moving forward. However, the
patch does brute force tactical fixes to the warnings like setting 0
to variables when we have "maybe-uninitialized". I was hoping by the
time I got to this point these things will be fixed.
The question now being, how should I go about upstreaming? Should I
just backport my gcc patches to gcc-11 and move forward? Or should I
work to fixup all of the GCC mainline issues the correct way? I think
the second option may take quite some time though.
-Stafford
[0] https://sourceware.org/glibc/wiki/NewPorts
[1] https://github.com/stffrdhrn/or1k-glibc/commit/e4336ce6d3ea6d86e4b4db73c6acbbc6de1d2c37
next reply other threads:[~2021-10-27 20:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 20:49 Stafford Horne [this message]
2021-10-27 22:13 ` Joseph Myers
2021-10-27 23:19 ` Stafford Horne
2021-10-28 17:15 ` Joseph Myers
2021-10-28 21:17 ` Stafford Horne
2021-10-28 21:45 ` Joseph Myers
2021-10-28 22:18 ` Stafford Horne
2021-10-29 9:05 ` Stafford Horne
2021-10-29 14:43 ` Joseph Myers
2021-10-29 15:08 ` Stafford Horne
2021-10-30 8:56 ` Stafford Horne
2021-11-01 20:47 ` Joseph Myers
2021-11-02 4:18 ` Stafford Horne
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=CAAfxs77MfWtYGYLgycvF0Utvq-rqbfaekCHAWL5R2bDLa3oKKQ@mail.gmail.com \
--to=shorne@gmail.com \
--cc=libc-alpha@sourceware.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).