public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/101867] avr libc build error for libstdc++
Date: Thu, 12 Aug 2021 12:19:54 +0000	[thread overview]
Message-ID: <bug-101867-4-6zWejbd8O6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101867-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to cqwrteur from comment #8)
> But it is not documented.

It is: https://gcc.gnu.org/install/configure.html#avr

> 
> in the /src/c++11/system_error.cc
> 
> #ifdef __AVR__
>       return std::error_condition(ev, std::system_category());
> #else
>       switch (ev)
>       {
> 
> #endif
> 
> i feel this switch is pointless.

Why do you feel that?

Have you read [syserr.errcat.objects] p4?

How do you think your suggestion for __AVR__ conforms to that requirement?


> https://github.com/vancegroup-mirrors/avr-libc/blob/master/avr-libc/include/
> errno.h
> 
> If you look at the errno.h here, it is pretty bad.

I don't know what you're saying here.

> I think this switch should just be removed.

How would you implement the requirement then?

  parent reply	other threads:[~2021-08-12 12:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 20:24 [Bug libstdc++/101867] New: " unlvsur at live dot com
2021-08-11 20:48 ` [Bug libstdc++/101867] " redi at gcc dot gnu.org
2021-08-11 20:51 ` unlvsur at live dot com
2021-08-11 20:58 ` unlvsur at live dot com
2021-08-11 21:00 ` unlvsur at live dot com
2021-08-11 21:04 ` unlvsur at live dot com
2021-08-11 21:53 ` unlvsur at live dot com
2021-08-11 22:09 ` redi at gcc dot gnu.org
2021-08-11 22:11 ` unlvsur at live dot com
2021-08-11 22:16 ` unlvsur at live dot com
2021-08-11 23:14 ` unlvsur at live dot com
2021-08-12 12:14 ` redi at gcc dot gnu.org
2021-08-12 12:19 ` redi at gcc dot gnu.org [this message]
2021-08-12 12:20 ` redi at gcc dot gnu.org
2021-08-12 16:52 ` unlvsur at live dot com
2021-08-12 17:29 ` redi at gcc dot gnu.org
2021-10-26 18:52 ` gjl at gcc dot gnu.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-101867-4-6zWejbd8O6@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).