public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/65881] no documentation of __uint128_t Date: Sat, 25 Apr 2015 05:50:00 -0000 [thread overview] Message-ID: <bug-65881-4-yqqv3aPqhq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65881-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65881 --- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> --- (In reply to Shawn Landden from comment #0) > gcc on x86_64 recognizes __uint128_t, but this is not documented along with > __int128, also there is no warning when a target does not support > __uint128_t, like there is with __int128: > > triangle64.c:32:1: error: ‘__int128’ is not supported for this target e.c:2:3: error: unknown type name ‘__uint128_t’ __uint128_t i=42; ^ > A unsigned 128-bit type is needed because it has defined integer overflow. https://gcc.gnu.org/onlinedocs/gcc/_005f_005fint128.html That type is called "unsigned __int128". The other aliases are only for compatibility or legacy. >From gcc-bugs-return-484601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 25 05:55:23 2015 Return-Path: <gcc-bugs-return-484601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 1609 invoked by alias); 25 Apr 2015 05:55:23 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 1584 invoked by uid 48); 25 Apr 2015 05:55:19 -0000 From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65880] [5/6 Regression] Member function issue with argument "pointer to const array of member function pointers" Date: Sat, 25 Apr 2015 05:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 5.1.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on short_desc everconfirmed cf_known_to_fail Message-ID: <bug-65880-4-DBvSHQYi1V@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-65880-4@http.gcc.gnu.org/bugzilla/> References: <bug-65880-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-04/txt/msg02153.txt.bz2 Content-length: 868 https://gcc.gnu.org/bugzilla/show_bug.cgi?ide880 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |rejects-valid Status|UNCONFIRMED |NEW Last reconfirmed| |2015-04-25 Summary|Member function issue with |[5/6 Regression] Member |argument "pointer to const |function issue with |array of member function |argument "pointer to const |pointers" |array of member function | |pointers" Ever confirmed|0 |1 Known to fail| |6.0
next prev parent reply other threads:[~2015-04-25 5:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-25 4:30 [Bug c/65881] New: " shawn at churchofgit dot com 2015-04-25 5:50 ` glisse at gcc dot gnu.org [this message] 2015-04-25 18:03 ` [Bug c/65881] " shawn at churchofgit 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-65881-4-yqqv3aPqhq@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: linkBe 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).