public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: "Fredrik Noring" <noring@nocrew.org>,
	"Matthew Fortune" <mfortune@gmail.com>,
	gcc-patches@gcc.gnu.org, "Jürgen Urban" <JuergenUrban@gmx.de>
Subject: Re: [PATCH] MIPS: Add `-mfix-r5900' option for the R5900 short loop erratum
Date: Thu, 15 Nov 2018 04:39:00 -0000	[thread overview]
Message-ID: <alpine.BSF.2.20.16.1811142337470.94650@arjuna.pair.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1811130049080.9637@eddie.linux-mips.org>

On Tue, 13 Nov 2018, Maciej W. Rozycki wrote:

> On Sun, 11 Nov 2018, Fredrik Noring wrote:
>
> > ../../../../libsanitizer/sanitizer_common/sanitizer_platform_limits_linux.cc:71:1: note: in expansion of macro ?COMPILER_CHECK?
> >    71 | COMPILER_CHECK(struct_kernel_stat_sz == sizeof(struct stat));
> >       | ^~~~~~~~~~~~~~
>
>  I guess `struct_kernel_stat_sz' and `sizeof(struct stat)' do not match.
> You may try making a preprocessed source with the same GCC invocation
> (possibly with `-dD' added if needed) to see how these items have been
> defined in your build environment.  This may reveal something obvious.
>
>  Also unless you realise the problem is due to misconfiguration, please
> file it in GCC bugzilla as a GCC 9 regression (since as you say 8.2.0
> builds just fine in your environment).  We don't want things to break with
> new releases.

This sounds familiar.

Perhaps the local edits I made for sanitizer support for MIPS
have been overwritten by the upstream import?  I know I made a
boo-boo and didn't "upstream" that.

brgds, H-P

      reply	other threads:[~2018-11-15  4:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 16:28 Fredrik Noring
2018-11-08 22:45 ` Maciej W. Rozycki
2018-11-09 18:43   ` Fredrik Noring
2018-11-09 22:30     ` mfortune
2018-11-10  9:32       ` Fredrik Noring
2018-11-11 12:31     ` Fredrik Noring
2018-11-13  1:00       ` Maciej W. Rozycki
2018-11-15  4:39         ` Hans-Peter Nilsson [this message]

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=alpine.BSF.2.20.16.1811142337470.94650@arjuna.pair.com \
    --to=hp@bitrange.com \
    --cc=JuergenUrban@gmx.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=macro@linux-mips.org \
    --cc=mfortune@gmail.com \
    --cc=noring@nocrew.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).