public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/105764] libgfortran fails to build with a custom thread model
Date: Sun, 09 Oct 2022 16:50:43 +0000	[thread overview]
Message-ID: <bug-105764-4-kkcGtccFiO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105764-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105764

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |ASSIGNED
                 CC|                            |aldot at gcc dot gnu.org,
                   |                            |egallager at gcc dot gnu.org
   Last reconfirmed|                            |2022-10-09
           Assignee|unassigned at gcc dot gnu.org      |lh_mouse at 126 dot com

--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
Taking conversation on the gcc-patches mailing list as confirmation:
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/602821.html

  reply	other threads:[~2022-10-09 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-29  3:33 [Bug libfortran/105764] New: " lh_mouse at 126 dot com
2022-10-09 16:50 ` egallager at gcc dot gnu.org [this message]
2022-10-10  7:26 ` [Bug libfortran/105764] " lh_mouse at 126 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=bug-105764-4-kkcGtccFiO@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).