From: Stafford Horne <shorne@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: GLIBC patches <libc-alpha@sourceware.org>
Subject: Re: Upstreaming OpenRISC with GCC mainline
Date: Sat, 30 Oct 2021 00:08:18 +0900 [thread overview]
Message-ID: <CAAfxs74D=ucBGYVFgbL3dsQY6uB6T8Mh5N-z5qQHAiKD_=Y59w@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110291442080.1788146@digraph.polyomino.org.uk>
On Fri, Oct 29, 2021, 11:43 PM Joseph Myers <joseph@codesourcery.com> wrote:
> On Fri, 29 Oct 2021, Stafford Horne wrote:
>
> > $ or1k-glibc-linux-gnu-gcc tst-mqueue5.c -c -std=gnu11
> -fgnu89-inline -g -O -Wall -Wwrite-strings -Wundef -Werror
> -fmerge-all-constants -frounding-math -fno-stack-protector -fno-c....
>
> That's -O, i.e. -O1, which is expected to have extra warnings. Making
> glibc build cleanly with different optimization options would be good, but
> should be handled separately from new ports.
>
Oh, you are right, I reset CFLAGS before the build so I didn't think
anything would be coming in. I'll try to figure out where those extra flags
are coming from.
>
next prev parent reply other threads:[~2021-10-29 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 20:49 Stafford Horne
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 [this message]
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='CAAfxs74D=ucBGYVFgbL3dsQY6uB6T8Mh5N-z5qQHAiKD_=Y59w@mail.gmail.com' \
--to=shorne@gmail.com \
--cc=joseph@codesourcery.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).