From: Ian Lance Taylor <ian@airs.com>
To: overseers@gcc.gnu.org
Subject: [gcc-bugzilla@gcc.gnu.org] Re: [Bug 26854]
Date: Wed, 26 Jan 2011 05:12:00 -0000 [thread overview]
Message-ID: <m3pqrkjljl.fsf@pepe.airs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 268 bytes --]
I got this e-mail message in response to a patch I committed to gcc.
The ChangeLog entry had a PR number. This message is coming from
bugzilla. I can't figure out what it means. I can't find any reference
to mro in bugzilla. Anybody know what this is about?
Ian
[-- Attachment #2: Type: message/rfc822, Size: 2759 bytes --]
From: gcc-bugzilla@gcc.gnu.org
To: ian@gcc.gnu.org
Subject: Re: [Bug 26854]
Date: Wed, 26 Jan 2011 01:26:53 +0000
Message-ID: <1477820948044148084934998490356@psmtp.com>
Can't locate mro.pm in @INC (@INC contains: . lib/i386-linux-thread-multi lib CODE(0x958d8b0) /usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.8.5 /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl)
ian wrote:
> Author: ian
> Date: Wed Jan 26 01:26:48 2011
> New Revision: 169267
>
> URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=169267
> Log:
> PR tree-optimization/26854
> * c-decl.c (struct c_scope): Add field has_jump_unsafe_decl.
> (decl_jump_unsafe): Move higher in file, with no other change.
> (bind): Set has_jump_unsafe_decl if appropriate.
> (update_label_decls): Test has_jump_unsafe_decl to avoid loop.
> (check_earlier_gotos): Likewise.
> (c_check_switch_jump_warnings): Likewise.
>
> Modified:
> trunk/gcc/ChangeLog
> trunk/gcc/c-decl.c
reply other threads:[~2011-01-26 5:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3pqrkjljl.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=overseers@gcc.gnu.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).