public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libmudflap/13505] [tree-ssa] libmudflap mf-hooks2.c build failure on cygwin Date: Thu, 10 Jun 2004 15:39:00 -0000 [thread overview] Message-ID: <20040610153940.8178.qmail@sourceware.org> (raw) In-Reply-To: <20031229205040.13505.fche@redhat.com> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-06-10 15:39 ------- Subject: Bug 13505 CVSROOT: /cvs/gcc Module name: gcc Changes by: fche@gcc.gnu.org 2004-06-10 15:39:33 Modified files: libmudflap : ChangeLog mf-hooks2.c Log message: 2004-06-10 Stephen Crowley <stephen.crowley@sbcglobal.net> PR libmudflap/13505 * mf-hooks2.c (semctl): Add cygwin porting hack. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libmudflap/ChangeLog.diff?cvsroot=gcc&r1=1.10&r2=1.11 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libmudflap/mf-hooks2.c.diff?cvsroot=gcc&r1=1.5&r2=1.6 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13505
next prev parent reply other threads:[~2004-06-10 15:39 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-12-29 21:08 [Bug libmudflap/13505] New: " fche at redhat dot com 2003-12-29 21:14 ` [Bug libmudflap/13505] " fche at redhat dot com 2003-12-29 21:15 ` pinskia at gcc dot gnu dot org 2004-03-09 18:34 ` [Bug libmudflap/13505] [tree-ssa] libmudflap " c dot christian dot joensson at comhem dot se 2004-04-20 11:08 ` c dot christian dot joensson at comhem dot se 2004-05-12 6:34 ` c dot christian dot joensson at comhem dot se 2004-06-02 20:01 ` fche at redhat dot com 2004-06-04 20:46 ` fche at redhat dot com 2004-06-07 23:28 ` pinskia at gcc dot gnu dot org 2004-06-10 9:20 ` c dot christian dot joensson at comhem dot se 2004-06-10 15:39 ` cvs-commit at gcc dot gnu dot org [this message] 2004-06-10 15:39 ` fche at redhat dot com
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=20040610153940.8178.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).