public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Paolo Carlini <paolo.carlini@oracle.com>
Cc: "Paul Pluzhnikov" <ppluzhnikov@google.com>,
	"Daniel Krügler" <daniel.kruegler@gmail.com>,
	"gcc-patches List" <gcc-patches@gcc.gnu.org>,
	libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [patch] Make vector::at() assertion message more useful (try #2)
Date: Mon, 23 Sep 2013 12:59:00 -0000	[thread overview]
Message-ID: <mvm1u4f4v81.fsf@hawking.suse.de> (raw)
In-Reply-To: <52402567.2080407@oracle.com> (Paolo Carlini's message of "Mon,	23 Sep 2013 06:26:31 -0500")

Paolo Carlini <paolo.carlini@oracle.com> writes:

> Paul, the *.cc are built with implicit instantiations disabled and we are
> missing explicit instantiations of this function template. If I remember
> correctly, we normally instantiate it in locale-inst.cc only for unsigned
> long and unsigned long long as second template argument. Thus, I would
> say, either make sure to use only those two in the new code, or add
> explicit instantiations. I would rather prefer the former, for example
> casting __val to (unsigned long long) in __concat_size_t isn't
> particularly elegant (vs for example checking if size_t isn't either
> unsigned long neither unsigned long long and adding an explicit
> instantiation only in that case)

What's wrong with always adding the instantiation?

> but would work I think. In any case, if it works for Andreas he is
> also preapproved to commit this kind change to unbreak his target.

There are a lot of targets using unsigned int for size_t, which would
have been uncovered by proper testing.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  parent reply	other threads:[~2013-09-23 11:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 20:53 Paul Pluzhnikov
2013-09-04 21:10 ` Daniel Krügler
2013-09-04 23:17   ` Paul Pluzhnikov
2013-09-05  4:55     ` Daniel Krügler
2013-09-13  5:19       ` Paul Pluzhnikov
2013-09-13 10:52         ` Paolo Carlini
2013-09-18 20:30           ` Paul Pluzhnikov
2013-09-18 23:24             ` Paolo Carlini
2013-09-22 10:19               ` Paul Pluzhnikov
2013-09-23 11:09             ` Andreas Schwab
2013-09-23 11:45               ` Paolo Carlini
2013-09-23 12:54                 ` Richard Biener
2013-09-23 12:59                 ` Andreas Schwab [this message]
2013-09-23 13:40                   ` Paolo Carlini
2013-09-23 13:42                     ` Andreas Schwab
2013-09-23 14:12                       ` Paolo Carlini
2013-09-23 14:12                     ` Marc Glisse
2013-09-23 14:12                       ` Jakub Jelinek
2015-04-06 11:37                       ` [wwwdocs] Testing C++ changes (was: [patch] Make vector::at() assertion message more useful) Gerald Pfeifer
2015-04-06 14:06                         ` [wwwdocs] Testing C++ changes Jason Merrill
2013-09-23 15:18                 ` [patch] Make vector::at() assertion message more useful (try #2) Paul Pluzhnikov
2013-09-23 15:26                   ` Paolo Carlini
2013-09-23 16:38                     ` Paul Pluzhnikov
2013-09-23 17:00                       ` Paolo Carlini
2013-09-23 17:01                         ` Paul Pluzhnikov
2013-09-23 16:21                   ` Paul Pluzhnikov
2013-09-04 23:26 ` Paolo Carlini
2013-09-04 23:36   ` Paul Pluzhnikov
2013-09-04 23:44     ` Paolo Carlini

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=mvm1u4f4v81.fsf@hawking.suse.de \
    --to=schwab@suse.de \
    --cc=daniel.kruegler@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=paolo.carlini@oracle.com \
    --cc=ppluzhnikov@google.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).