public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/33190] tm.texi describes some non-existing hooks Date: Sat, 25 Aug 2007 19:14:00 -0000 [thread overview] Message-ID: <20070825191419.32593.qmail@sourceware.org> (raw) In-Reply-To: <bug-33190-2433@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pinskia at gcc dot gnu dot org 2007-08-25 19:14 ------- RANGE_TEST_NON_SHORT_CIRCUIT was renamed to LOGICAL_OP_NON_SHORT_CIRCUIT but the doc was not updated. 2004-11-18 Nathan Sidwell <nathan@codesourcery.com> Nathan, can you please update the docs for this target macro? -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nathan at codesourcery dot | |com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33190
next prev parent reply other threads:[~2007-08-25 19:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-08-25 17:38 [Bug target/33190] New: " kai-gcc-bugs at khms dot westfalen dot de 2007-08-25 19:14 ` pinskia at gcc dot gnu dot org [this message] 2007-09-25 18:38 ` [Bug target/33190] " kai-gcc-bugs at khms dot westfalen dot de [not found] <bug-33190-4@http.gcc.gnu.org/bugzilla/> 2012-02-06 23:58 ` pinskia at gcc dot gnu.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=20070825191419.32593.qmail@sourceware.org \ --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: linkBe 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).