public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gcc-bugs@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: Compilation of rust-demangle.c fails on MinGW
Date: Wed, 04 Aug 2021 16:51:45 +0300	[thread overview]
Message-ID: <83czqtl3m6.fsf@gnu.org> (raw)
In-Reply-To: <878s1hwcxj.fsf@igel.home> (message from Andreas Schwab on Wed, 04 Aug 2021 15:35:04 +0200)

> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Richard Sandiford <richard.sandiford@arm.com>,  Eli Zaretskii
>  <eliz@gnu.org>
> Date: Wed, 04 Aug 2021 15:35:04 +0200
> 
> On Aug 04 2021, Eli Zaretskii via Gcc-bugs wrote:
> 
> > I'd love to, but please tell me where.  I couldn't find any
> > information about reporting libiberty bugs, sorry if I missed
> > something obvious.
> 
> The libiberty README says to report bugs to gcc-bugs@gcc.gnu.org.

Yes, and that's what I did eventually.  But I was then told by Richard
Sandiford that that address is "mostly a bugzilla feed and so isn't widely
read".


  reply	other threads:[~2021-08-04 13:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31 12:56 Eli Zaretskii
2021-08-04 12:04 ` Richard Sandiford
2021-08-04 12:17   ` Eli Zaretskii
2021-08-04 13:03     ` Jonathan Wakely
2021-08-04 13:49       ` Eli Zaretskii
2021-08-04 13:35     ` Andreas Schwab
2021-08-04 13:51       ` Eli Zaretskii [this message]
2021-08-04 14:41       ` Jonathan Wakely
2021-08-04 15:45         ` Eli Zaretskii
2021-08-04 18:57           ` Andrew Pinski
2021-08-04 19:14             ` Eli Zaretskii

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=83czqtl3m6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=richard.sandiford@arm.com \
    --cc=schwab@linux-m68k.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).