> its kind of silly, and this allows us to remove a few more #ifdefs.
>
> bootstrapped + regtest x86_64-linux-gnu, ok?
No, I don't think so, because:
> #if FRAME_POINTER_REGNUM != ARG_POINTER_REGNUM
> -#if HARD_FRAME_POINTER_IS_ARG_POINTER
> +#if HARD_FRAME_POINTER_REGNUM == ARG_POINTER_RE
Our libstdc++/ page dates back to when libstdc++ was merged into GCC in
2000, 0x10 years ago. It has been a mostly empty shell for most of that
time period and hardly seen any updates in the last decade.
So, after https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01467.html I
suggest to streamline
From: Trevor Saunders
Hi,
its kind of silly, and this allows us to remove a few more #ifdefs.
bootstrapped + regtest x86_64-linux-gnu, ok?
Trev
gcc/ChangeLog:
2016-08-20 Trevor Saunders
* rtl.h (HARD_FRAME_POINTER_IS_ARG_POINTER): Remove definition.
(enum global_rtl_index
From: Trevor Saunders
Hi,
basically just $subject, always define HAVE_AS_LEB128, and then use if / else
instead of #ifdef. Note the diff has a bit of whitespace noise, so there's a
-w diff below the full one.
bootstrapped and regtested on x86_64-linux-gnu, ok?
Trev
gcc/ChangeLog:
2016-08-2
On 20 August 2016 at 11:22, ayush goel wrote:
>>
>> We're talking about a one-line change, but this is absolutely
>> crucial and central to use of gnulib. Until this is correct,
>> any previous host-specific testing is invalid, unfortunately.
>>
>> In the previous revision, you had:
>>
>> INCGNU =
I merely split _M_dfs() into small functions to see how it goes. It
turns out to save half of the stack consumption in -O0 without
observable performance impact.
If we want, we can use __attribute__((always_inline)) and
__attribute__((noinline)) to make those handler functions back and
forth for r
>
> We're talking about a one-line change, but this is absolutely
> crucial and central to use of gnulib. Until this is correct,
> any previous host-specific testing is invalid, unfortunately.
>
> In the previous revision, you had:
>
> INCGNU = -I../gnulib -I$(srcdir)/../gnulib/import
>
> and I was
Working on something else, I noticed that in news.html we have various
references to libstdc++/ (the libstdc++ "micro site") for further
information. Except there really isn't much further information
there, so let's remove those links.
(This also is in preparation of another, forthcoming patch
> Turning it into a compile test that counts the number of jumps threaded
> seems potentially flaky but I'm not against it. And I'm not sure how to
> reliably turn it into an execution test. Would the directives
>
> /* { dg-do run } */
> /* { dg-require-effective-target avx2 } */
> /* { dg-requ
On Sat, Aug 20, 2016 at 09:02:37AM +0200, Florian Weimer wrote:
> Does this mean that with this patch, glibc should remove its
> _FORTIFY_SOURCE warning for non-optimized builds when compiling under
> GCC >= 7?
Of course not, you really need optimizations for _FORTIFY_SOURCE to be
useful.
On Fri, Aug 19, 2016 at 04:30:47PM -0600, Martin Sebor wrote:
> The patch looks bigger than it actually is because:
>
> 1) It modifies the return type of the function to bool rather than
>unsigned HOST_WIDE_INT representing the object size (this was
>necessary to avoid having its callers m
Hi!
Currently C++ does not warn at all when built-in functions are re-defined
with a different signature, while C does warn on that even without -Wall.
Thus I'd like to propose a -Wall enabled warning for that in C++.
Initially I tried to warn unconditionally but that made too many tests
in the
* Martin Sebor:
> As requested in the review of the following patch
>
> https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01363.html
>
> attached is the small enhancement to compute_builtin_object_size to
> make the function usable even without optimization without the full
> overhead of the tree-ob
13 matches
Mail list logo
