public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109688] SPDLOG build fails with C++20 and -DSPDLOG_USE_STD_FORMAT=1
Date: Mon, 01 May 2023 20:02:39 +0000	[thread overview]
Message-ID: <bug-109688-4-dYUPgEOJuS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109688-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jamaika from comment #4)
> https://github.com/gabime/spdlog/blob/v1.x/example/example.cpp
> ```
> for %%f in ("example.cpp") do g++.exe -v -std=gnu++20 -march=x86-64-v2
> -ftree-vectorize -g0 -O3 -fPIC -mavx -mxsave -mpclmul -maes
> -DSPDLOG_USE_STD_FORMAT=1 -c %%f -o %%~nf.o
> ```

That will not work as example.cpp depends on the spdlog headers.

PLEASE again have the exact directions on how to test this.
Also just like your previous bugs, this is lacking that. Maybe also report the
failure to the developer of spdlog since it is not obvious if it is a
libstdc++, C++ front-end bug or just a problem with spdlog.

Note saying spdlog works with MSVC does not mean it is still not buggy code.

  parent reply	other threads:[~2023-05-01 20:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01 19:41 [Bug c++/109688] New: Build fail " lukaszcz18 at wp dot pl
2023-05-01 19:45 ` [Bug c++/109688] SPDLOG build fails " pinskia at gcc dot gnu.org
2023-05-01 19:46 ` pinskia at gcc dot gnu.org
2023-05-01 19:51 ` lukaszcz18 at wp dot pl
2023-05-01 19:54 ` lukaszcz18 at wp dot pl
2023-05-01 20:02 ` pinskia at gcc dot gnu.org [this message]
2023-05-01 20:39 ` rs2740 at gmail 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-109688-4-dYUPgEOJuS@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).