Greetings,
This is rather on the trivial side. Google fuzzer found signed integer
overflow in d_number, given this input: _ZZccDF2147483647
Google ref: b141647507.
Ok for trunk?
Thanks,
libiberty/ChangeLog
2019-10-28 Paul Pluzhnikov
* cp-demangle (d_number): Avoid signed int
Greetings,
For google b/9650176, attached patch adds bounds checks to std::array
and updates expected line numbers in tests.
This is similar to the checks that we do for std::vector.
See also https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56109
Committed as r226465.
Thanks,
--
Paul Pluzhnikov
e mean time, r212208 deleted the doubling.
Thanks,
--
Paul Pluzhnikov
On Fri, Jun 27, 2014 at 12:51 PM, Jason Merrill wrote:
> On 06/27/2014 11:04 AM, Paul Pluzhnikov wrote:
>>
>> Ok to backport r210653 (fix for PR58930) to gcc-4_9-branch?
>
>
> OK, yes.
Thanks. Committed attached patch as r212207.
Tested on Linux/x86_64, no regressio
inly no objections from me. Just ask on the mailing list: if Jason
> agrees,
> please go ahead. Thanks.
Ok to backport r210653 (fix for PR58930) to gcc-4_9-branch?
(If not, I'll backport to google/gcc-4_9 instead.)
Thanks,
--
Paul Pluzhnikov
cessary/useful with asan?
>
> This was some unrelated change. Paul?
That appears to have been a merge mistake on my part.
I'll add them back. Thanks for noticing.
--
Paul Pluzhnikov
t Report Var(ix86_ld_pie_copyrelocs) Init(0)
+Use linker copy relocs for pie
They are not "linker copy relocs", they are simply "copy relocations".
So I would call the option "-mcopy-relocs" and be done with that. But this
is just bike-shedding :-)
LGTM.
--
Paul Pluzhnikov
> Add -f[no-]skeleton-type-units flag to control whether GCC
> generates skeleton type units.
>
> This patch is for the google/gcc-4_8 branch.
Ok for Google branch.
Thanks,
--
Paul Pluzhnikov
Ping?
On Fri, Mar 21, 2014 at 9:16 AM, Paul Pluzhnikov wrote:
> Greetings,
>
> To fix PR59295, this patch moves (generally useless) warning about
> repeated / redundant friend declarations under -Wredundant-decls.
>
> Tested on Linux/x86_64 with no regressions.
>
> Ok fo
Greetings,
To fix PR59295, this patch moves (generally useless) warning about
repeated / redundant friend declarations under -Wredundant-decls.
Tested on Linux/x86_64 with no regressions.
Ok for trunk once it opens in stage 1?
Thanks,
--
2014-03-21 Paul Pluzhnikov
PR c++/59295
On Fri, Mar 21, 2014 at 1:58 AM, Fabien Chêne wrote:
> Why not making this warning suppressable, instead of removing it ?
> Shouldn't it fall under -W(no)-redundant-decls ?
Thanks. I'll revise the patch to do that.
--
Paul Pluzhnikov
hanks,
Google ref: b/11542609
--
2014-03-20 Paul Pluzhnikov
PR c++/59295
* gcc/cp/friend.c (add_friend): Remove complain parameter.
(do_friend): Adjust.
* gcc/cp/cp-tree.h (add_friend): Adjust.
* gcc/cp/pt.c (instantiate_class_template_1): Adjust.
Jakub,
On Mon, Feb 10, 2014 at 12:09 AM, Jakub Jelinek wrote:
> On Tue, Feb 04, 2014 at 04:59:14PM -0800, Paul Pluzhnikov wrote:
>> gcc/testsuite/ChangeLog:
>>
>> 2014-02-04 Paul Pluzhnikov
>>
>> * gcc.dg/vect/no-vfa-vect-depend-2.c (main1): Fix buf
Ping?
On Tue, Feb 4, 2014 at 5:08 PM, Paul Pluzhnikov wrote:
> +cc jakub
>
> On Tue, Feb 4, 2014 at 4:59 PM, Paul Pluzhnikov
> wrote:
>> Greetings,
>>
>> The gcc.dg/vect/no-vfa-vect-depend-2.c failed for us, when linked with
>> gold, but not when linked wi
+cc jakub
On Tue, Feb 4, 2014 at 4:59 PM, Paul Pluzhnikov wrote:
> Greetings,
>
> The gcc.dg/vect/no-vfa-vect-depend-2.c failed for us, when linked with
> gold, but not when linked with BFD ld.
>
> The problem appears to be off-by-one error causing array out of bounds
> acce
Greetings,
The gcc.dg/vect/no-vfa-vect-depend-2.c failed for us, when linked with
gold, but not when linked with BFD ld.
The problem appears to be off-by-one error causing array out of bounds
access, fixed by attached patch.
OK for trunk?
Thanks,
gcc/testsuite/ChangeLog:
2014-02-04 Paul
Greetings,
We test GCC without access to the build tree (we only have convenient access to
install and source trees).
Building libgomp.c/affinity-1.c and libgomp.c++/affinity-1.C fails in
such testing, because of '#include "config.h"' which is nowhere to be
found.
Is that a bug?
Should I open a
Greetings,
For Google b/9127283, I've committed attached patch on google/gcc-4_8 branch.
Related: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56109
This caught ~10 bugs for us. erase(end()) and pop_back() on empty
vector appear to be most common.
--
Paul Pluzhnikov
Index: libstdc++-v3/in
Greetings,
I've finished backport of r202818 from trunk to google/gcc-4_8 as r206071.
Thanks,
--
Paul Pluzhnikov
Index: libstdc++-v3/include/debug/array
===
--- libstdc++-v3/include/debug/array(revision 206038)
+++ libstdc
Greetings,
I've reverted r203873 and r203036 in r204860 on google/gcc-4_8 branch.
The r203036 changes output of std::sort when input has equivalent
elements, and this breaks "golden output" tests, which we'll need to
clean up.
Thanks,
--
Paul Pluzhnikov
Ian?
Ping x4.
On Wed, Sep 18, 2013 at 4:24 PM, Paolo Carlini wrote:
>>> Original message:
>>> http://gcc.gnu.org/ml/gcc-patches/2013-08/msg00394.html
>>
>>
> I'm adding Ian in CC.
--
Paul Pluzhnikov
Greetings,
For Google b/10860844, I've committed the patch below on google gcc-4_8
(r203381) and integration (r203382) branches.
This forces abi-version to be the latest available.
2013-10-10 Paul Pluizhnikov
* gcc/common.opt (flag_abi_version): Set to 0.
Index: gcc/common.opt
==
Greetings,
I committed partial backport of r202818, r202832 and r202836 to
google/gcc-4_8 branch as r202927.
2013-09-25 Paul Pluzhnikov
* libstdc++-v3/config/abi/pre/gnu.ver: Add
_ZSt24__throw_out_of_range_fmtPKcz
* libstdc++-v3/src/c++11/Makefile.am: Add snprintf_lite
On Mon, Sep 23, 2013 at 6:29 PM, Paul Pluzhnikov wrote:
> I've committed the patch below to google/integration (r202856) and
> gcc-4_8 (r202857) branches. Google ref: b/10872448.
I've committed r202880 to adjust line numbers for libstdc++ breakage
on google/gcc-4_8 branch.
Tha
Greetings,
I've committed the patch below to google/integration (r202856) and
gcc-4_8 (r202857) branches. Google ref: b/10872448.
This cought approximately 10 bugs in our code.
See also r195357 (similar checks for std::vector) and PR 56109.
Thanks,
2013-09-23 Paul Pluzh
On 9/23/13 9:24 AM, Paolo Carlini wrote:
Does this look right?
Yes. Nit, in the comment I would also explicitly mention locale-inst.cc.
Done, submitted as r202836.
2013-09-23 Paul Pluzhnikov
* src/c++11/snprintf_lite.cc (__concat_size_t): Use
unsigned long long
On 9/23/13 7:54 AM, Paolo Carlini wrote:
Testing this patch:
In fact, however, that unsigned long long instantiation isn't
*unconditionally* available, see locale-inst.cc.
Thanks,
I think we have to use
unsigned long as a fall back controlled by the same macro. And please
add a comment expl
On 9/23/13 7:48 AM, Paul Pluzhnikov wrote:
Testing this patch:
libstdc++ tests finished with
RUNTESTFLAGS='--target_board=unix\{-m32,-m64\}'
Committed as r202832.
Sorry about the trouble.
--
2013-09-23 Paul Pluzhnikov
* src/c++11/snprintf_lite.cc (__concat_size_t)
On 9/23/13 4:26 AM, Paolo Carlini wrote:
m68k-linux/./libstdc++-v3/src/.libs/libstdc++.so: undefined reference
to `int std::__int_to_char(char*, unsigned int,
char const*, std::_Ios_Fmtflags, bool)'
Reproduced on i686.
Sorry about the trouble ...
I would say, either make sure to use only tho
at are failing there independently of my patch.
Committed as r202818.
Thanks,
--
Paul Pluzhnikov
.S. In the process of updating callers of __throw_out_of_range, I've
discovered that two of them had already used __builtin_sprintf.
P.P.S. Sorry this patch grew ... I can split it into parts if that's easier
to review.
--
Paul Pluzhnikov
libstdc++-v3/ChangeLog:
* include/bits/functexcept
* gcc.dg/torture/pr58417.c: New testcase.
Thanks,
--
Paul Pluzhnikov
Ping x3?
2013/9/11 Paul Pluzhnikov :
> Ping x2?
>
> Original message:
> http://gcc.gnu.org/ml/gcc-patches/2013-08/msg00394.html
Thanks,
--
Paul Pluzhnikov
_... functions.
I've added the new snprintf.cc to c++11/ rather than c++98/ as Paolo
suggested, because the only current caller is in c++11/functexcept.cc
Thanks,
--
Paul Pluzhnikov
libstdc++-v3/ChangeLog:
2013-09-12 Paul Pluzhnikov
* src/c++11/Makefile.am: Add snprintf.cc
Ping x2?
Original message:
http://gcc.gnu.org/ml/gcc-patches/2013-08/msg00394.html
On Fri, Aug 16, 2013 at 6:10 PM, Paul Pluzhnikov wrote:
> Ping?
--
Paul Pluzhnikov
ite(), or ...?
Is the location of the out-of-line code in libstdc++-v3/libsupc++/ ok?
(Would probably be called snprintf_lite.cc or some such.)
Is the version I've assigned to the symbol -- GLIBCXX_3.4.20 -- ok?
Thanks,
--
Paul Pluzhnikov
lly" transformed inside
__index_out_of_range_msg into the final message, making translation
more difficult.
2. __index_out_of_range_msg() would have to return a string, which is heavier
weight (in try#1 I just used snprintf, which was considered "too heavy").
Thanks,
--
Paul Pluzhnikov
"this->size() (which is %zu)"), __n, this->size());
[The patch also doesn't include libstdc++-v3/libsupc++/Makefile.in,
which I'll regenerate before submitting.]
[Please CC me on any replies.]
--
Paul Pluzhnikov
2013-09-04 Paul Pluzhnikov
* libstd
Ping?
On Wed, Aug 7, 2013 at 11:51 AM, Paul Pluzhnikov wrote:
> The following source:
>
> template static void f();
> void g() { f(); }
>
> results in "_Z1fIiEvv" under g++, but in "_ZL1fIiEvv" under clang.
>
> Richard Smith says:
>
>
Greetings,
I've committed r201755 on google/gcc-4_8 branch as r201761.
On Wed, Aug 7, 2013 at 11:34 AM, Andrew Pinski wrote:
> I think this should also be send to the GCC List as libiberty is
> officially maintained by GCC.
http://gcc.gnu.org/ml/gcc-patches/2013-08/msg00394.html
Thanks,
--
Paul Pluzhnikov
o argue that this is a 'g++' bug (since there is no
ABI violation here), but c++filt should be able to handle this, and does
with attached patch.
Ok for trunk?
Thanks,
Google ref: b/10137049
---
Paul Pluzhnikov
2013-08-07 Paul Pluzhnikov
* cp-demangle.c (d_name): Handle i
Greetings,
I committed merge of r201068 (backport of the fix for PR57878 from
trunk) as r201071 to google/gcc-4_8 branch.
Thanks,
--
Paul Pluzhnikov
--
Paul Pluzhnikov
On Thu, May 30, 2013 at 10:00 PM, Paul Pluzhnikov
wrote:
> I've committed attached patch on google/gcc-4_8 branch to fix testsuite
> failures broken by r199468.
Also applied to google/integration branch.
--
Paul Pluzhnikov
I've committed attached patch on google/gcc-4_8 branch to fix testsuite
failures broken by r199468.
Thanks,
--
Paul Pluzhnikov
Index:
libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/assign_neg.cc
===
---
li
On Thu, May 30, 2013 at 6:48 PM, Diego Novillo wrote:
> OK. Is this applicable to trunk and/or release branches?
No: the "cheap" vector and string checks are on google branches only.
--
Paul Pluzhnikov
version linked in
with new code, and failing the check.
Google ref b/9198806
Attached patch relaxes the check, while still catching dangling vector
accesses.
Ok for google/gcc_4-7, gcc-4_8 and integration branches?
Thanks,
--
Paul Pluzhnikov
Index: libstdc++-v3/include/bits/stl_vector.h
Jonathan,
On Thu, May 23, 2013 at 10:13 AM, Paul Pluzhnikov
wrote:
> On Thu, May 23, 2013 at 9:14 AM, Jonathan Wakely
> wrote:
>
>> I was wondering the other day whether we should put these checks on
>> trunk and enable them automatically when !defined(__OPTIMIZE__)
&
these checks.
--
Paul Pluzhnikov
+cc libstd...@gcc.gnu.org
On Thu, May 23, 2013 at 8:51 AM, Paul Pluzhnikov wrote:
> Greetings,
>
> This patch adds (relatively) cheap bounds and dangling checks to
> vector, similar to the checks I added to vector in r195373,
> r195356, etc.
>
> Ok for google branc
Greetings,
This patch adds (relatively) cheap bounds and dangling checks to
vector, similar to the checks I added to vector in r195373,
r195356, etc.
Ok for google branches (gcc-4_7, gcc-4_8, integration) ?
Thanks,
--
Index: libstdc++-v3/include/bits/stl_bvector.h
Greetings,
I've commited the patch below on google/gcc-4_7 branch (r198071) to XFAILs
gcc.dg/lto/20100430-1 on powerpc*.
Index: contrib/testsuite-management/powerpc64-grtev3-linux-gnu.xfail
===
--- contrib/testsuite-management/pow
that's how I understood you.
I don't believe it would be easy to implement such interposer (if
possible at all), and it would be very much tied to glibc internals.
Overriding CPUID at loader initialization time sounds simpler (but I
haven't looked at the code yet :-).
--
Paul Pluzhnikov
t of libgcc.
LD_CPU_FEATURES=sse,sse2 ./a.out # run as if only sse and sse2 are available
Thanks,
--
Paul Pluzhnikov
nterposer.
Roland explained to me ~15 years ago why it is that way (it had something to
do with Hurd); an explanation I can't find at the moment.
--
Paul Pluzhnikov
at 50x.
--
Paul Pluzhnikov
malloc
... takes loader lock ... takes malloc lock
malloc _Unwind_Backtrace
... needs malloc lock dl_iterate_phdr
held by T2... needs loader lock held by T1
--
Paul Pluzhnikov
t too ...
Thanks,
--
Paul Pluzhnikov
not in the recent past)
suitable for the unwinder requirements that people have?
Thanks,
--
Paul Pluzhnikov
when
you collect stack traces across live production services).
I hope this answers your question.
--
Paul Pluzhnikov
Greetings,
Google ref b/8187733
Build libstdc++-v3/src/c++11/debug.cc with -fno-omit-frame-pointer, so
frame-based unwinder can step through it.
Tested: bootstrap build and verified debug.cc is built with
-fno-omit-frame-pointer.
Ok for google/gcc-4_7 and google/integration?
Thanks,
--
Paul
email us again during Stage 1 :-)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56109
> Googlers, please include the libstdc++ list on patches to the
> libstdc++ code, even if it's only to a google branch.
Will do. Sorry about that.
Thanks,
--
Paul Pluzhnikov
This patch allows us to catch use of destructed strings.
Google ref: b/5430313
Ok for google/gcc-4_7 and google/integration?
--
Paul Pluzhnikov
Index: libstdc++-v3/include/ext/sso_string_base.h
===
--- libstdc++-v3/include/ext
This patch sets destructed vector into an invalid state, such that
subsequent calls to begin(), end(), size(), etc. all throw logic_error.
Google ref b/7248326
Ok for google/gcc-4_7 and google/integration?
Thanks,
--
Paul Pluzhnikov
Index: libstdc++-v3/include/bits/stl_vector.h
On Sun, Jan 20, 2013 at 3:16 AM, Gerald Pfeifer wrote:
> Isn't the error message wrong, then?
Thanks for catching that! Updated patch attached.
--
Paul Pluzhnikov
Index: libstdc++-v3/include/bits/stl_vector.h
===
--- libs
This patch adds lightweight checks for front()/back() on empty vector.
Google ref b/7939186
Ok for google/gcc-4_7 and google/integration branches?
--
Paul Pluzhnikov
Index: libstdc++-v3/include/bits/stl_vector.h
===
--- libstdc
Ok for google/gcc-4_7 ?
Ref b/8003094
Thanks,
--
Paul Pluzhnikov
2013-01-15 Paul Pluzhnikov
PR 55982
* strncat-chk.c (__strncat_chk): Fix loop unroll.
Index: libssp/strncat-chk.c
===
--- libssp/strncat-chk.c
Greetings,
In libssp/strncat-chk.c, the loop was unrolled 5 times (apparently by
accident).
Ok for trunk?
Thanks,
--
Paul Pluzhnikov
2013-01-14 Paul Pluzhnikov
PR 55982
* strncat-chk.c (__strncat_chk): Fix loop unroll.
Index: libssp/strncat-chk.c
sive"
{ target c++98 } 19 }
+// { dg-message "17:\\(if you use '-fpermissive' G\\+\\+ will accept
your code\\)" "-fpermissive" { target c++98 } 19 }
(Minor adjustment to the expected error message).
error12.C is identical on trunk and google/gcc-4_7.
Thanks,
--
Paul Pluzhnikov
On Fri, Jan 4, 2013 at 9:41 AM, Xinliang David Li wrote:
> ok.
The patch as sent caused some breakage, I had to adjust test cases a bit.
Submitting attached patch.
Thanks,
--
Paul Pluzhnikov
Index: gcc/testsuite/g++.old-deja/g++.other/crash2
Back-port revision 194909 to google/gcc-4_7 branch:
http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=194909
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54526
Google ref: b/7427993
Index: gcc/testsuite/g++.old-deja/g++.other/crash28.C
===
012-12/msg01271.html to the
> google 4.7 branch.
Approved for google/gcc-4_7 branch.
Thanks,
--
Paul Pluzhnikov
Greetings,
This patch is for google/gcc-4_7 branch.
Thanks,
2012-11-05 Paul Pluzhnikov
* contrib/testsuite-management/powerpc-grtev3-linux-gnu.xfail:
extend expiration date for pr54127.
Index: contrib/testsuite-management/powerpc-grtev3-linux-gnu.xfail
On Wed, Sep 5, 2012 at 6:26 PM, Ollie Wild wrote:
> Okay for google/integration and google/gcc-4_7?
Approved for google/* branches.
Thanks,
--
Paul Pluzhnikov
On Wed, Sep 5, 2012 at 7:46 PM, Cary Coutant wrote:
> This patch is for the google/gcc-4_7 branch.
Approved for google/gcc-4_7 branch.
Thanks,
--
Paul Pluzhnikov
On Wed, Aug 22, 2012 at 5:11 PM, Cary Coutant wrote:
> This patch is for the google/gcc-4_7 branch.
Approved for google/gcc-4_7 branch.
Thanks,
--
Paul Pluzhnikov
On Fri, Aug 3, 2012 at 2:56 PM, Sriraman Tallam wrote:
> This patch reverts the original implementation of CPU runtime detection
Ok for google/gcc-4_7 branch
--
Paul Pluzhnikov
see that we are not alone:
http://old.nabble.com/-patch--libgomp%3A-removing-nodlopen-flag-for-portability-td10286039.html
Generally we don't use OpenMP, but some of our third-party libraries
do depend on it.
Thanks for the heads-up.
--
Paul Pluzhnikov
b/6368405
Google ref b/6156799
Tested: make && make check
2012-04-22 Paul Pluzhnikov
* libgomp/configure.tgt: Don't force initial-exec.
Index: libgomp/configure.tgt
===
--- libgomp/configure.tgt (re
thread to finish
}
Or
ptr = new Foo;
DoSomethingThatDeletes(ptr);
ptr->x++; // Oops. Use after free
AFAICT, neither of these would be helped by delete stomping on the pointer.
--
Paul Pluzhnikov
ging allocator that makes
> pages dirty after free.
Agreed. I'll rename __is_valid to _M_is_valid to match the rest of the file,
and submit to google/integration only.
Thanks for your comments,
--
Paul Pluzhnikov
e top of every member
Sorry, no. Adding "assert(this);" does not catch any new bugs (at least
not on Linux) -- the code would have immediately crashed on zero-page
dereference anyway.
Thanks,
--
Paul Pluzhnikov
did catch real bugs doesn't mean it's a good idea,
> as you say, those bugs probably could have been caught in other ways.
Sure -- we have other ways to catch the these bugs. They are not very
practical at the moment due to their runtime overhead.
As for your other suggestion: enabling _GLIBCXX_DEBUG just for vector,
that didn't occur to me and is something I'd like to explore.
Thanks,
--
Paul Pluzhnikov
On Tue, Sep 6, 2011 at 10:46 AM, Diego Novillo wrote:
> On Tue, Sep 6, 2011 at 12:54, Paul Pluzhnikov wrote:
>> On Tue, Sep 6, 2011 at 9:44 AM, Diego Novillo wrote:
>>
>>> OK. Any reason not to send this (or a variant) to mainline?
>>
>> AFAIU, mainline is
parallel" debug modes is undesirable.
Unfortunately, _GLIBCXX_DEBUG makes no performance guarantees (making some
normally constant-time operations O(N), etc.) and so we can't just turn
it on in Google.
Thanks,
--
Paul Pluzhnikov
On Tue, Sep 6, 2011 at 9:28 AM, Paul Pluzhnikov wrote:
> This patch adds a lightweight self-consistency check to many vector
> operations. Google issue 5246356.
Sorry, forgot to mention: tested by doing bootstrap and make check on
Linux/x86_64.
--
Paul Pluzhnikov
Greetings,
This patch adds a lightweight self-consistency check to many vector
operations. Google issue 5246356.
Ok for google/integration branch?
Thanks,
--
2011-09-06 Paul Pluzhnikov
* include/bits/stl_vector.h (__is_valid): New function.
(begin, end, size, capacity
On Fri, May 20, 2011 at 8:10 AM, Ollie Wild wrote:
> Ok, for google/integration. Please integrate to google/main and
> google/gcc-4_6 as well.
Done: r173959, r173960, r173961.
Thanks,
--
Paul Pluzhnikov
This patch is for google/integration branch.
Sorry about not setting the markers correctly.
Tested by doing a bootstrap build and verifying that
__gnu_cxx::__verbose_terminate_handler is built with frame pointers.
On Thu, May 19, 2011 at 10:46 AM, Paul Pluzhnikov
wrote:
> 2011-05-19 P
2011-05-19 Paul Pluzhnikov
* libstdc++-v3/libsupc++/Makefile.am: Add -fno-omit-frame-pointer
to vterminate.
* libstdc++-v3/libsupc++/Makefile.in: Regenerate.
Index: libstdc++-v3/libsupc++/Makefile.in
On Wed, May 11, 2011 at 4:01 PM, Eric Botcazou wrote:
> No gcc/ prefix in the ChangeLog file of the gcc/ directory. See other
> entries.
Fixed. Sorry about that.
--
Paul Pluzhnikov
ted though -- if you want to get the same output you get from
'gcc', you need to examine 'gcc -v' very carefully. And, as Jakub
noted, linking directly with 'ld' is discouraged.
Thanks,
--
Paul Pluzhnikov
ay with me, and I gather from the
>> thread that you are fine with that as well.
>
> Given the build system changes, the gcc.c changes are OK.
Ok for trunk then?
I'll wait till tomorrow in case someone has additional comments on the
desirability part.
Thanks!
--
Paul Pluzhnikov
Ping? Ping? Ping? Ping? Ping?
http://gcc.gnu.org/ml/gcc-patches/2011-04/msg00246.html
CC'ing the rest of build system maintainers.
On Mon, May 2, 2011 at 8:56 AM, Paul Pluzhnikov wrote:
> On Mon, May 2, 2011 at 7:59 AM, Joseph S. Myers
> wrote:
>
> Thanks for your comments.
[I've started with two ...]
Thanks!
--
Paul Pluzhnikov
Ping? Ping? Ping? Ping?
This is getting ridiculous. Would someone please accept the patch,
tell me what to fix in it to make it acceptable, or explain why it is
a bad idea?
Thanks!
On Mon, Apr 25, 2011 at 9:08 AM, Paul Pluzhnikov wrote:
> Ping? Ping? Ping?
>
> On Mon, Apr 18, 2011 a
Ping? Ping? Ping?
On Mon, Apr 18, 2011 at 9:45 AM, Paul Pluzhnikov wrote:
> Ping? Ping?
>
> On Mon, Apr 11, 2011 at 11:00 AM, Paul Pluzhnikov
> wrote:
>> Ping?
--
Paul Pluzhnikov
Ping? Ping?
On Mon, Apr 11, 2011 at 11:00 AM, Paul Pluzhnikov
wrote:
> Ping?
--
Paul Pluzhnikov
This patch adds lightweight debug checks (if enabled by macros).
To be applied only to google/integration branch.
Tested by bootstrapping and running "make check".
2011-04-12 Paul Pluzhnikov
* libstdc++-v3/include/bits/stl_algo.h: Add comparator debug checks
1 - 100 of 105 matches
Mail list logo
