public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/29276] sim/mips/sim-main.h:41:25: error: conversion from ‘long long unsigned int’ to ‘unsigned_word’
Date: Sun, 23 Oct 2022 18:29:37 +0000	[thread overview]
Message-ID: <bug-29276-4717-sDbitLaz2H@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29276-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29276

--- Comment #1 from Mike Frysinger <vapier at gentoo dot org> ---
pretty sure the warning was in there in older versions, the diff with gdb-12 is
that we enabled -Werror (since it was building cleanly for the few targets i
checked)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2022-10-23 18:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 19:02 [Bug sim/29276] New: " hector.oron at gmail dot com
2022-10-23 18:29 ` vapier at gentoo dot org [this message]
2022-10-23 19:44 ` [Bug sim/29276] mips: mips.igen:1453:15: " vapier at gentoo dot org
2022-10-23 19:49 ` vapier at gentoo dot org
2022-11-04  0:45 ` vapier at gentoo dot org
2022-11-08  7:57 ` vapier at gentoo dot org

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=bug-29276-4717-sDbitLaz2H@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).