public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/36044] user-requested backtrace
Date: Sat, 03 Mar 2012 07:46:00 -0000	[thread overview]
Message-ID: <bug-36044-4-f7u1ghot4T@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-36044-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36044

Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |patch
                URL|                            |http://gcc.gnu.org/ml/fortr
                   |                            |an/2012-03/msg00015.html
                 CC|                            |fxcoudert at gcc dot
                   |                            |gnu.org

--- Comment #7 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> 2012-03-03 07:45:51 UTC ---
Patch was proposed at http://gcc.gnu.org/ml/fortran/2012-03/msg00015.html


       reply	other threads:[~2012-03-03  7:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-36044-4@http.gcc.gnu.org/bugzilla/>
2012-03-03  7:46 ` fxcoudert at gcc dot gnu.org [this message]
2012-12-19 16:30 ` janus at gcc dot gnu.org
2012-12-20 18:15 ` janus at gcc dot gnu.org
2012-12-20 19:36 ` janus at gcc dot gnu.org
2008-04-25 12:20 [Bug libfortran/36044] New: " jaydub66 at gmail dot com
2008-04-27 18:44 ` [Bug libfortran/36044] " fxcoudert at gcc dot gnu dot org
2008-04-28 15:45 ` jaydub66 at gmail dot com
2008-04-28 16:42 ` burnus at gcc dot gnu dot org
2008-04-28 21:37 ` tkoenig at gcc dot gnu dot org
2009-02-22 22:33 ` fxcoudert at gcc dot gnu dot org
2009-02-23  4:37 ` jvdelisle 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=bug-36044-4-f7u1ghot4T@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).