public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47103] i386 options have multi-line descriptions
Date: Wed, 29 Dec 2010 11:26:00 -0000 [thread overview]
Message-ID: <bug-47103-4-9tGoNDYW2j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47103-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47103
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2010-12-29 11:26:09 UTC ---
On Wed, 29 Dec 2010, goeran at uddeborg dot se wrote:
> In gcc/config/i386/i386.opt there are multi-line descriptions of the options
> mvzeroupper and mdispatch-scheduler. Only the first line is picked up fro
> translation, and according to bug 34352, comment 1, it is a bug for those files
> to have multi-line descriptions.
Multi-line descriptions don't appear to be mentioned in doc/options.texi,
but if they are to be considered invalid then the opt*.awk code really
ought to reject them rather than combining the lines (and if they are
valid, they should be documented and po/exgettext should support them).
prev parent reply other threads:[~2010-12-29 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 11:01 [Bug target/47103] New: " goeran at uddeborg dot se
2010-12-29 11:26 ` joseph at codesourcery dot com [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=bug-47103-4-9tGoNDYW2j@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).