From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: fshahbazker@wavecomp.com, "Héctor Orón Martínez" <hector.oron@gmail.com>
Subject: Re: Account auto-locked due to spam. mipsel simulator fails to build.
Date: Wed, 22 Jun 2022 20:56:20 +0200 [thread overview]
Message-ID: <YrNl1LWs7+uPiQ2A@wildebeest.org> (raw)
In-Reply-To: <CAODfWeFXr7Za6oEk1ApXaw-2EJscpwvZm5Kr0T+=vvbV-shd5Q@mail.gmail.com>
Hi Héctor,
On Wed, Jun 22, 2022 at 08:06:12PM +0200, Héctor Orón Martínez via Overseers wrote:
> I was trying to open a bug report on simulator build failure for
> mipsel, then I got locked. Could you please unlock me?
Unlocked.
Sorry, I don't immediately know what triggered the spam lock. I would
suggest trying to remove the "/<<PKGBUILDDIR>>/" strings when trying
to report it again. And/Or removing the fancy quotes.
Cheers,
Mark
> The content for the bug was:
>
> When building mipsel simulator, on GDB 12.1, build fails with:
>
> In file included from support.c:25:
> /<<PKGBUILDDIR>>/sim/mips/mips.igen: In function ‘do_dmfc1b’:
> /<<PKGBUILDDIR>>/sim/mips/sim-main.h:41:25: error: conversion from
> ‘long long unsigned int’ to ‘unsigned_word’ {aka ‘unsigned int’}
> changes value from ‘16045693110240459472’ to ‘3134241488’
> [-Werror=overflow]
> 41 | #define SET64HI(t) (((uword64)(t))<<32)
> | ^
> /<<PKGBUILDDIR>>/sim/mips/mips.igen:1453:15: note: in expansion of
> macro ‘SET64HI’
> 1453 | GPR[rt] = SET64HI (0xDEADC0DE) | 0xBAD0BAD0;
> | ^~~~~~~
>
> Full log: https://buildd.debian.org/status/fetch.php?pkg=gdb&arch=mipsel&ver=12.1-1&stamp=1655916813&raw=0
>
> Build was fine on 11.2 release.
>
> --
> Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
prev parent reply other threads:[~2022-06-22 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 18:06 Héctor Orón Martínez
2022-06-22 18:56 ` Mark Wielaard [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=YrNl1LWs7+uPiQ2A@wildebeest.org \
--to=mark@klomp.org \
--cc=fshahbazker@wavecomp.com \
--cc=hector.oron@gmail.com \
--cc=overseers@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).