From: i.nixman@autistici.org
To: NightStrike <nightstrike@gmail.com>
Cc: Eric Botcazou <botcazou@adacore.com>,
fortran@gcc.gnu.org, libstdc++@gcc.gnu.org,
gcc-patches@gcc.gnu.org
Subject: Re: Adding a new thread model to GCC
Date: Sat, 24 Dec 2022 06:27:34 +0000 [thread overview]
Message-ID: <df1fdfcea9aa5ae9bf3114f6135fd4f6@autistici.org> (raw)
In-Reply-To: <CAF1jjLvvhC5goxY=i0O3tSeO4X97Fdv2c_X9ec9zHCOtBBMzCg@mail.gmail.com>
On 2022-12-24 05:58, NightStrike wrote:
>
> I think this might have broken fortran. I'm assuming because the
> backtrace includes gthr.h, and I just did a git pull:
>
> In file included from /tmp/rtmingw/mingw/include/windows.h:71,
> from ../libgcc/gthr-default.h:606,
> from ../../../libgfortran/../libgcc/gthr.h:148,
> from ../../../libgfortran/io/io.h:33,
> from ../../../libgfortran/runtime/error.c:27:
> ../../../libgfortran/io/io.h:298:24: error: expected identifier before
> numeric constant
> 298 | { CC_LIST, CC_FORTRAN, CC_NONE,
> | ^~~~~~~
hmm...
I don't remember if I specified `fortran` in `--enable-language` in my
test builds...
will try to build again now...
next prev parent reply other threads:[~2022-12-24 6:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 18:34 LIU Hao
2022-10-01 20:02 ` Bernhard Reutner-Fischer
2022-10-21 9:58 ` Jonathan Wakely
2022-10-21 10:09 ` i.nixman
2022-10-21 10:48 ` Jonathan Wakely
2022-10-21 10:55 ` i.nixman
2022-10-21 11:36 ` LIU Hao
2022-10-21 11:54 ` i.nixman
2022-10-21 12:19 ` LIU Hao
2022-10-21 12:34 ` i.nixman
2022-10-24 3:40 ` LIU Hao
2022-10-24 20:50 ` Jacek Caban
2022-10-21 11:44 ` Eric Botcazou
2022-10-21 11:55 ` i.nixman
2022-10-24 6:53 ` i.nixman
2022-10-24 8:15 ` Eric Botcazou
2022-10-24 8:20 ` i.nixman
2022-10-31 9:18 ` Eric Botcazou
2022-10-31 15:22 ` i.nixman
2022-11-01 5:22 ` i.nixman
2022-11-01 9:09 ` Eric Botcazou
2022-11-02 12:05 ` i.nixman
2022-11-02 21:27 ` Eric Botcazou
2022-11-02 21:40 ` i.nixman
2022-12-16 17:18 ` Jonathan Wakely
2022-12-16 19:20 ` Eric Botcazou
2022-12-22 12:21 ` Jonathan Yong
2022-12-22 12:28 ` i.nixman
2022-12-23 23:59 ` Jonathan Yong
2022-12-24 5:58 ` NightStrike
2022-12-24 6:27 ` i.nixman [this message]
2022-12-24 13:50 ` i.nixman
2022-12-24 15:42 ` i.nixman
2022-12-24 15:57 ` i.nixman
2022-12-24 21:22 ` i.nixman
2022-12-25 1:10 ` Jonathan Yong
2023-01-09 21:56 ` Eric Botcazou
2022-12-24 6:22 ` i.nixman
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=df1fdfcea9aa5ae9bf3114f6135fd4f6@autistici.org \
--to=i.nixman@autistici.org \
--cc=botcazou@adacore.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=nightstrike@gmail.com \
/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).