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 preprocessor/30468] [4.0/4.1/4.2/4.3 Regression] -M not fully chops dirname Date: Mon, 15 Jan 2007 02:34:00 -0000 [thread overview] Message-ID: <20070115023426.31493.qmail@sourceware.org> (raw) In-Reply-To: <bug-30468-13905@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pinskia at gcc dot gnu dot org 2007-01-15 02:34 ------- Confirmed. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pinskia at gcc dot gnu dot | |org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Known to fail|4.1.1 |4.1.1 4.0.0 4.0.2 4.3.0 Known to work|3.4.4 |3.4.4 3.4.0 Last reconfirmed|0000-00-00 00:00:00 |2007-01-15 02:34:25 date| | Summary|-M not fully chops dirname |[4.0/4.1/4.2/4.3 Regression] | |-M not fully chops dirname Target Milestone|--- |4.0.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30468
next prev parent reply other threads:[~2007-01-15 2:34 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-15 2:17 [Bug preprocessor/30468] New: " kaminaga at sm dot sony dot co dot jp 2007-01-15 2:34 ` pinskia at gcc dot gnu dot org [this message] 2007-01-20 4:24 ` [Bug preprocessor/30468] [4.0/4.1/4.2/4.3 Regression] " tromey at gcc dot gnu dot org 2007-01-21 23:30 ` patchapp at dberlin dot org 2007-01-30 15:50 ` tromey at gcc dot gnu dot org 2007-01-30 16:30 ` [Bug preprocessor/30468] [4.0/4.1/4.2 " tromey at gcc dot gnu dot org 2007-02-03 21:25 ` gdr at gcc dot gnu dot org 2007-02-03 21:27 ` pinskia at gcc dot gnu dot org 2007-02-05 5:52 ` mmitchel at gcc dot gnu dot org 2007-02-14 9:20 ` mmitchel at gcc dot gnu dot org 2007-04-23 14:26 ` tromey at gcc dot gnu dot org 2007-04-23 14:27 ` tromey at gcc dot gnu dot org 2007-04-23 14:27 ` tromey at gcc dot gnu 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=20070115023426.31493.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).