public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/100057] There are no freestanding C++
Date: Tue, 13 Apr 2021 10:32:14 +0000 [thread overview]
Message-ID: <bug-100057-4-mYtWjT2Us5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100057-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100057
cqwrteur <unlvsur at live dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #27 from cqwrteur <unlvsur at live dot com> ---
(In reply to Jonathan Wakely from comment #25)
> (In reply to Jonathan Wakely from comment #24)
> > This is a regression, please report a separate bug about this part.
>
> Reported as Bug 100060, fix already written (because when you report a
> clear, focused bug report about specific issues, it gets dealt with).
I would like to say I would rather fixing bugs by myself instead of reporting
because I find issues every day.
How to commit code to gcc? what's the permission requirement?
next prev parent reply other threads:[~2021-04-13 10:32 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 0:22 [Bug libstdc++/100057] New: " unlvsur at live dot com
2021-04-13 0:26 ` [Bug libstdc++/100057] " unlvsur at live dot com
2021-04-13 0:29 ` unlvsur at live dot com
2021-04-13 0:44 ` unlvsur at live dot com
2021-04-13 0:58 ` unlvsur at live dot com
2021-04-13 1:34 ` phdofthehouse at gmail dot com
2021-04-13 1:36 ` phdofthehouse at gmail dot com
2021-04-13 1:53 ` unlvsur at live dot com
2021-04-13 1:57 ` unlvsur at live dot com
2021-04-13 2:20 ` unlvsur at live dot com
2021-04-13 2:21 ` unlvsur at live dot com
2021-04-13 2:49 ` unlvsur at live dot com
2021-04-13 3:58 ` unlvsur at live dot com
2021-04-13 4:36 ` unlvsur at live dot com
2021-04-13 5:12 ` unlvsur at live dot com
2021-04-13 7:50 ` unlvsur at live dot com
2021-04-13 8:12 ` unlvsur at live dot com
2021-04-13 8:14 ` unlvsur at live dot com
2021-04-13 8:46 ` rguenth at gcc dot gnu.org
2021-04-13 8:48 ` unlvsur at live dot com
2021-04-13 8:51 ` unlvsur at live dot com
2021-04-13 8:57 ` rguenth at gcc dot gnu.org
2021-04-13 9:06 ` unlvsur at live dot com
2021-04-13 9:24 ` redi at gcc dot gnu.org
2021-04-13 9:27 ` redi at gcc dot gnu.org
2021-04-13 9:41 ` redi at gcc dot gnu.org
2021-04-13 10:01 ` unlvsur at live dot com
2021-04-13 10:32 ` unlvsur at live dot com [this message]
2021-04-13 10:50 ` redi at gcc dot gnu.org
2021-08-21 8:50 ` unlvsur at live dot com
2021-08-23 10:08 ` redi at gcc dot gnu.org
2021-08-23 10:16 ` unlvsur at live dot com
2021-08-23 10:19 ` unlvsur at live dot com
2021-12-29 22:17 ` pixel@nobis-crew.org
2021-12-29 23:04 ` pixel@nobis-crew.org
2021-12-29 23:57 ` unlvsur at live dot com
2021-12-29 23:57 ` unlvsur at live dot com
2021-12-30 10:19 ` redi at gcc dot gnu.org
2021-12-30 10:25 ` redi at gcc dot gnu.org
2021-12-30 10:56 ` redi at gcc dot gnu.org
2021-12-30 11:31 ` redi at gcc dot gnu.org
2021-12-30 18:37 ` unlvsur at live dot com
2021-12-30 18:39 ` unlvsur at live 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-100057-4-mYtWjT2Us5@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).