lass from the
lang_hooks class in the frontend and override any of its virtual methods.
--
Regards,
Mikhail Maltsev
ons
> are hardcoded and quite wrong for big tables...
>
> Also what is the codesize difference on SPEC2006/2017? I don't see
> any mention of performance impact either...
>
> Wilco
--
Regards,
Mikhail Maltsev
Hi. Yes, bug maintenance is appreciated. See this message and replies
to it: https://gcc.gnu.org/ml/gcc/2016-04/msg00258.html .
I'm not sure that there is a documented policy, but I might be wrong.
--
Regards,
Mikhail Maltsev
tin
>>
>> Excellent; thanks.
>
> Hello.
>
> I've just done that, periodically built LCOV can be found here:
>
> http://gcc.opensuse.org/gcc-lcov/
>
>>
>> For your periodic builds, please can you add "jit" to the enabled
>> languages (it will also need --enable-host-shared).
>
> Done that and will be seen in next build. I do it every weekend.
>
>>
>> Would be nice to add libiberty and libcpp to this, but maybe that needs
>> extra work?
>
> Yep, it's currently done for gcc subfolder. Can be done in the future.
>
> Martin
>
>>
>> Dave
>>
>
--
Regards,
Mikhail Maltsev
at 'bar' comes before 'foo', the error in 'foo' is not diagnosed.
I did not dive into details, but my speculation is that the parser enters some
strange state and skips 'foo' entirely (-fdump-tree-gimple contains only 'bar').
If I add another function after 'foo', it is handled correctly.
Any ide
When parsing SSA names, we should check that parent names are scalars.
In fact, this patch just uses the condition of a 'gcc_assert' in
'make_ssa_name_fn'.
--
Regards,
Mikhail Maltsev
gcc/testsuite/ChangeLog:
2017-05-01 Mikhail Maltsev <malts...@gmail.com>
* gcc.dg/gi
This patch deals with invalid __MEM construct. Before we start building an
expression for __MEM, we must check that parsing succeeded and that the __MEM
operand is a pointer.
--
Regards,
Mikhail Maltsev
gcc/c/ChangeLog:
2017-05-01 Mikhail Maltsev <malts...@gmail.com>
*
This is essentially the same problem as in patch 2, but with unary '*'. We
should verify that its argument is a pointer.
--
Regards,
Mikhail Maltsev
gcc/c/ChangeLog:
2017-05-01 Mikhail Maltsev <malts...@gmail.com>
* gimple-parser.c (c_parser_gimple_unary_expression):
This bug happens when the LHS of operator '->' is either missing, i.e.:
(->a) = 0;
or it is not a pointer:
int b;
b_2->c = 0;
LHS should be validated.
--
Regards,
Mikhail Maltsev
gcc/testsuite/ChangeLog:
2017-05-01 Mikhail Maltsev <malts...@gmail.com>
* gcc.dg
'c_parser_error', but this function does not handle
locations very well (in fact, it uses input_location).
--
Regards,
Mikhail Maltsev
gcc/testsuite/ChangeLog:
2017-05-01 Mikhail Maltsev <malts...@gmail.com>
* gcc.dg/gimplefe-error-4.c: New test.
* gcc.dg/gimplefe-error-5.
(although, I see some noise in the tree-prof tests). The patches are intended
for GCC 8.
--
Regards,
Mikhail Maltsev
m/blog/archives/499
>
> and do not miss the comment by Joel Brobecker about what AdaCore uses
> (internally?).
>
>
And probably this talk is also somewhat relevant (Cauldron 2013 - DejaGNU BOF):
https://www.youtube.com/watch?v=rjm-n9EgxiE
--
Mikhail Maltsev
bgcc), for libc++ (~ libstdc++).
All utilities (~ libiberty) live in the LLVM repo (include/llvm/ADT,
include/llvm/Support, lib/Support). Other projects, like LLDB, are checked out
into a subdirectory, and are always built from the combined tree.
--
Regards,
Mikhail Maltsev
.
--
Mikhail Maltsev
t.
Shouldn't this also go to the wiki?
--
Mikhail Maltsev
On 05/23/2016 05:15 PM, Kyrill Tkachov wrote:
>
> expand_simple_binop may fail. I think you should add a check that diff_rtx is
> non-NULL
> and bail out early if it is.
>
Fixed.
--
Regards,
Mikhail Maltsev
diff --git a/gcc/ifcvt.c b/gcc/ifcvt.c
index a9c146b..e1473eb 1
15-11/msg01773.html
--
Regards,
Mikhail Maltsev
This patch adds a new if-conversion pattern for the following case:
if (test) x = A; else x = B;
A and B are constants, abs(A - B) == 2^N, A != 0, B != 0
Bootstrapped and regtested on x86_64-linux. OK for trunk?
--
Regards,
Mikhail Maltsev
gcc/testsuite/ChangeLog:
2016-05-23
and uses it to select the
correct branch. Also, ISTM that the last 'else' branch is unreachable.
Bootstrapped and regtested on x86_64-linux. OK for trunk?
--
Regards,
Mikhail Maltsev
gcc/ChangeLog:
2016-05-23 Mikhail Maltsev <malts...@gmail.com>
* i
,
Mikhail Maltsev
On 05/17/2016 06:09 PM, Richard Biener wrote:
>
> The patch is ok.
>
Committed as r236344.
--
Regards,
Mikhail Maltsev
On 05/17/2016 04:39 PM, Richard Biener wrote:
>
> Are you sure narrowing conversions are valid for rotates?
>
> (char)short_var < byte.
>
Yes, but the transformation leaves conversions as-is. Only bit_not is removed.
--
Regards,
Mikhail Maltsev
I might be wrong!
Some of the C++ Core Guidelines checks are already implemented in clang-tidy:
http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/cppcoreguidelines/
--
Regards,
Mikhail Maltsev
ink it can currently cause
> issues for these particular transformations.
Fixed.
>
> I don't know if we might want some :c / single_use restrictions, maybe on the
> outer convert and the rshift/rotate.
>
I don't think :c can be used here. As for :s, I added it, as you suggested.
Als
On 05/10/2016 10:51 PM, Joseph Myers wrote:
> On Sat, 9 Apr 2016, Mikhail Maltsev wrote:
>
>> gcc/c/ChangeLog:
>>
>> 2016-04-08 Mikhail Maltsev <malts...@gmail.com>
>>
>> PR c/43651
>> * c-decl.c (declspecs_add_qual): Warn when
On 05/08/2016 10:57 PM, Marc Glisse wrote:
> On Sun, 8 May 2016, Mikhail Maltsev wrote:
>
>> Hi!
>>
>> I decided to revive this patch:
>> https://gcc.gnu.org/ml/gcc-patches/2015-06/msg00999.html.
>> I addressed review comments about sign conversions. Bootstr
Hi!
I decided to revive this patch:
https://gcc.gnu.org/ml/gcc-patches/2015-06/msg00999.html.
I addressed review comments about sign conversions. Bootstrapped and regtested
on x86_64-linux-gnu {,-m32}. OK for trunk?
--
Regards,
Mikhail Maltsev
gcc/testsuite/ChangeLog:
2016-05-08 Mikhail
On 04/10/2016 11:12 PM, Martin Sebor wrote:
> On 04/09/2016 06:28 AM, Mikhail Maltsev wrote:
>> On 04/08/2016 08:54 PM, Martin Sebor wrote:
>>>> The name for new option "-Wduplicate-decl-specifier" and wording was
>>>> chosen to match the same option
te(void*, std::size_t, const std::nothrow_t&);
void operator delete[](void*, std::size_t, const std::nothrow_t&);
IIUC, 'delete(void*, std::size_t)' is used by default in C++14
(https://gcc.gnu.org/ml/gcc-patches/2014-12/msg01266.html). How should we handle
this?
--
Regards,
Mikhail Maltsev
. Below is a
> draft I came up with. Thoughts?
>
Probably contrib/clang-format and https://gcc.gnu.org/wiki/FormattingCodeForGCC
are also worth mentioning.
--
Regards,
Mikhail Maltsev
ECF_FREE.
Fixed.
--
Regards,
Mikhail Maltsev
diff --git a/gcc/ada/gcc-interface/trans.c b/gcc/ada/gcc-interface/trans.c
index 357d26f..00e4f84 100644
--- a/gcc/ada/gcc-interface/trans.c
+++ b/gcc/ada/gcc-interface/trans.c
@@ -400,7 +400,7 @@ gigi (Node_Id gnat_root,
ftype,
-linux-gnu.
--
Regards,
Mikhail Maltsev
gcc/c/ChangeLog:
2016-04-16 Mikhail Maltsev <malts...@gmail.com>
* c-decl.c (merge_decls): Handle free_flag.
gcc/ChangeLog:
2016-04-16 Mikhail Maltsev <malts...@gmail.com>
* builtin-attrs.def: Add at
t; Also, in C11 mode, Clang issues the warning for duplicated
> _Atomic qualifiers but it doesn't look like GCC would with
> the patch. Here again, unless there's some reason not to,
> I would expect GCC to issue the same warning as Clang for
> the same code.
>
Fixed.
--
Regards,
Mikhail M
On 04/08/2016 12:50 AM, Joseph Myers wrote:
> New options need documenting in invoke.texi.
>
Done.
--
Regards,
Mikhail Maltsev
gcc/c/ChangeLog:
2016-04-08 Mikhail Maltsev <malts...@gmail.com>
PR c/43651
* c-decl.c (declspecs_add_qual): Warn when -Wdu
was
chosen to match the same option in Clang.
Bootstrapped and regtested on x86_64-linux. OK for next stage 1?
--
Regards,
Mikhail Maltsev
gcc/c/ChangeLog:
2016-04-04 Mikhail Maltsev <malts...@gmail.com>
PR c/43651
* c-decl.c (declspecs_add_qual): Warn when
nts (//), which C-family
frontends already understand.
>
> Also note my suggestion that all GIMPLE sources should be valid C as well it
> would be unfortunate to lose the option to torture unit tests.
>
I wonder how will this work with SSA form?
--
Regards,
Mikhail Maltsev
d we build "co_await p.yield_value(e)"
from it and further expand co_await?
--
Regards,
Mikhail Maltsev
diff --git a/.gitignore b/.gitignore
index c9a6158..4595d5e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -37,6 +37,9 @@ TAGS.sub
.clang-format
+.agignore
+.ycm_extra_conf.py
+
you please elaborate on that?
>
> Ciao,
> Michael.
>
--
Regards,
Mikhail Maltsev
refactoring iterators in GCC 7?
--
Regards,
Mikhail Maltsev
e stack
You actually don't need to use any complex memory management stuff. GCC
provides a wrapper for malloc called 'xmalloc'. It works like normal
malloc, but aborts in case of allocation failure.
--
Regards,
Mikhail Maltsev
to see an example of it's usage.
Good luck!
P.S. I also CC'd this message to one of major contributors to GCC diagnostics
module, maybe he could add something.
--
Regards,
Mikhail Maltsev
trap-asan".
OK for trunk?
--
Regards,
Mikhail Maltsev
ChangeLog:
2016-01-24 Mikhail Maltsev <malts...@gmail.com>
PR bootstrap/69329
* Makefile.in: Regenerate.
* Makefile.tpl (BASE_FLAGS_TO_PASS): Add LSAN_OPTIONS.
diff --git a/Makefile.in b/Makefile
ntrib/lvimrc. Settings for emacs are available here:
https://gcc.gnu.org/wiki/FormattingCodeForGCC
> Should I star looking at the "easy hacks" ?
Yes, probably it's a good point to start with.
--
Regards,
Mikhail Maltsev
y set, so 'default-src' is used as a fallback."
I think, this can be fixed by replacing 'style="color:red"' with 'class="..."'
and adding the corresponding CSS class to the stylesheet.
--
Regards,
Mikhail Maltsev
o
instrumentation. In just enables consistency checks of the compiler's
internal state, i.e. it is more related to debugging GCC itself.
--
Regards,
Mikhail Maltsev
st.cgi?keywords=easyhack_id=135581=---
--
Regards,
Mikhail Maltsev
On 11/24/2015 02:43 AM, Bernd Schmidt wrote:
> On 11/24/2015 12:09 AM, Mikhail Maltsev wrote:
>> The attached patch fixes a problem introduced in r229567: the assertion
>>
>> gcc_assert (is_sse);
>>
>> is checked if flag_checking is false, and this causes an I
Hi!
The attached patch fixes a problem introduced in r229567: the assertion
gcc_assert (is_sse);
is checked if flag_checking is false, and this causes an ICE when compiling with
-fno-checking.
Bootstrapped and regtested on x86_64-pc-linux-gnu. OK for trunk?
--
Regards,
Mikhail Maltsev
testcases
are objects which store metainformation (such as name) and have methods
for running tests.
--
Regards,
Mikhail Maltsev
On 11/01/2015 11:34 PM, Bernhard Reutner-Fischer wrote:
> Mikhail,
>
> On November 1, 2015 9:19:19 PM GMT+01:00, Mikhail Maltsev
> <malts...@gmail.com> wrote:
>> This patch cleans up remaining bits related to ENABLE_CHECKING. After
>> applying
>> this patch
}
>> }
> I think this condition was reversed, right?
>
> Please fix that and install on the trunk.
>
> Thanks again!
>
> jeff
Fixed and committed as r229756.
--
Regards,
Mikhail Maltsev
On 11/03/2015 02:35 AM, Jeff Law wrote:
> This is good fore the trunk too. Please install.
>
> Thanks!
>
> jeff
Committed as r229758.
--
Regards,
Mikhail Maltsev
for trunk?
--
Regards,
Mikhail Maltsev
gcc/c-family/ChangeLog:
2015-10-31 Mikhail Maltsev <malts...@gmail.com>
* c-omp.c (c_omp_split_clauses): Remove conditional compilation. Use
flag_checking.
gcc/cp/ChangeLog:
2015-10-31 Mikhail Maltsev <malts...@gmail.com
-checking=release.
libcpp/ChangeLog:
2015-11-01 Mikhail Maltsev <malts...@gmail.com>
* config.in: Regenerate.
* configure: Regenerate.
* configure.ac: Remove ENABLE_CHECKING.
gcc/ChangeLog:
2015-11-01 Mikhail Maltsev <malts...@gmail.com>
al value got from
command-line options).
--
Regards,
Mikhail Maltsev
On 10/26/2015 12:47 PM, Richard Biener wrote:
> I committed the attached to fix build with the valgrind annotations active.
>
> Richard.
>
Doh! Sorry for breakage.
--
Regards,
Mikhail Maltsev
t'll be faster than checking
> flag_checking.
I fixed this and other issues, and committed the attached patch.
--
Regards,
Mikhail Maltsev
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 81d0e1c..d8a22c3 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,9 @@
+2015-10-26 Mikhail Maltsev <
e
Vary: Accept-Encoding
403 Forbidden
Forbidden
You don't have permission to access /ftp/
on this server.
Apache Server at gcc.gnu.org Port 80
Just in case, my IP is 185.6.245.180.
--
Regards,
Mikhail Maltsev
course it will be easy for me to adjust the patch to whatever the
final decision will be.
--
Regards,
Mikhail Maltsev
internal debugging option (and is also rather small), I
think it's OK to commit it without approve (as obvious).
Bootstrapped and regtested on x86_64-pc-linux-gnu.
--
Regards,
Mikhail Maltsev
gcc/ChangeLog:
2015-10-18 Mikhail Maltsev <malts...@gmail.com>
PR other
On 10/06/2015 03:59 PM, Richard Biener wrote:
> On Tue, Oct 6, 2015 at 2:46 PM, Bernd Schmidt <bschm...@redhat.com> wrote:
>> On 10/06/2015 01:39 AM, Mikhail Maltsev wrote:
>>>
>>> void verify_insn_chain (void);
>>> +static inline void checki
rts into the first patch of the series. As for
replacing linemap_assert, I hope it can be done separately.
--
Regards,
Mikhail Maltsev
libcpp/ChangeLog:
2015-10-19 Mikhail Maltsev <malts...@gmail.com>
* include/line-map.h: Use CHECKING_P instead of ENABLE_CHECKING.
P in genextract, and always enable debugging
functions in gengtype.
--
Regards,
Mikhail Maltsev
gcc/ChangeLog:
2015-10-19 Mikhail Maltsev <malts...@gmail.com>
* genautomata.c: Use CHECKING_P instead of ENABLE_CHECKING.
* genconditions.c: Define CHECKING_P
On 10/06/2015 03:45 PM, Richard Biener wrote:
> On Tue, Oct 6, 2015 at 2:41 PM, Bernd Schmidt <bschm...@redhat.com> wrote:
>> On 10/06/2015 01:32 AM, Mikhail Maltsev wrote:
>>>
>>> gcc/ChangeLog:
>>>
>>> 2015-10-05 Mikhail Maltsev
some of the other updated parts today, and I
also hope to get in time with the whole series (before stage1 ends).
--
Regards,
Mikhail Maltsev
gcc/ChangeLog:
2015-10-18 Mikhail Maltsev <malts...@gmail.com>
* config.in: Regenerate.
* configure: Regenerate.
* confi
On 10/06/2015 04:46 PM, Jason Merrill wrote:
> Hi, sorry for the slow response. Please feel free to ping once a week.
>
> On 08/27/2015 02:27 PM, Mikhail Maltsev wrote:
>> + if (TREE_THIS_VOLATILE (t) && (!DECL_P (t) || want_rval))
>
> Why the !DECL_P
ewise, for libstdc++ benchmark.
--
Regards,
Mikhail Maltsev
l and
gcc/Makefile.in in more detail.
Finally, note that GCC has some means of test coverage analysis: you can
configure/build it with "--disable-bootstrap --enable-coverage", run the tests
and then use gcov.
--
Regards,
Mikhail Maltsev
gcc/ChangeLog:
2015-10-05 Mikhail Maltsev <malts...@gmail.com>
* attribs.c (check_attribute_tables): Define new function.
(init_attributes): Use it.
* cfgcleanup.c (try_optimize_cfg): Use flag_checking.
* cfgexpand.c (expand_goto, expand_debug_expr): Li
gcc/ChangeLog:
2015-10-05 Mikhail Maltsev <malts...@gmail.com>
* config/alpha/alpha.c (alpha_function_arg): Use gcc_checking_assert.
* config/arm/arm.c (arm_unwind_emit_sequence): Adjust to use CHECKING_P.
* config/bfin/bfin.c (hwloop_optimize): Li
PING.
On 08/27/2015 09:27 PM, Mikhail Maltsev wrote:
> Hi.
> This patch fixes a rejects-valid bug related to volatile-qualified arguments
> of
> constexpr functions. This is essentially a one-line change in constexpr.c.
> Bootstrapped and regtested on x86_64-pc-linux-gnu. OK for
gcc/java/ChangeLog:
2015-10-05 Mikhail Maltsev <malts...@gmail.com>
* decl.c (java_mark_decl_local): Use flag_checking instead of
ENABLE_CHECKING.
gcc/ada/ChangeLog:
2015-10-05 Mikhail Maltsev <malts...@gmail.com>
* gcc-interface/decl.c (gnat_to_gnu_
gcc/ChangeLog:
2015-10-05 Mikhail Maltsev <malts...@gmail.com>
* alloc-pool.h (base_pool_allocator::initialize, ::allocate,
::remove): Adjust to use CHECKING_P.
>From ed727b2279dd36e2fbf1ab6956270cbd487b1a01 Mon Sep 17 00:00:00 2001
From: Mikhail Maltsev <malts.
,
Mikhail Maltsev
gcc/ChangeLog:
2015-10-05 Mikhail Maltsev <malts...@gmail.com>
* common.opt: Add flag_checking.
* system.h (CHECKING_P): Define.
libcpp/ChangeLog:
2015-10-05 Mikhail Maltsev <malts...@gmail.com>
* system.h (CHECKING_P, gcc_checking_assert): D
libcpp/ChangeLog:
2015-10-05 Mikhail Maltsev <malts...@gmail.com>
* include/line-map.h: Fix use of ENABLE_CHECKING.
* init.c: Likewise.
* macro.c (struct macro_arg_token_iter, set_arg_token,
macro_arg_token_iter_init, macro_arg_token_iter_f
gcc/fortran/ChangeLog:
2015-10-05 Mikhail Maltsev <malts...@gmail.com>
* trans-common.c (create_common): Adjust to use flag_checking.
* trans.c (gfc_add_modify_loc): Use gcc_checking_assert.
>From 8113b4d5bc943772145abdd6562d4af6093d9718 Mon Sep 17 00:00:00 2001
From
gcc/ChangeLog:
2015-10-05 Mikhail Maltsev <malts...@gmail.com>
* genautomata.c: Use CHECKING_P instead of ENABLE_CHECKING.
* genconditions.c: Define CHECKING_P in generated code.
* genextract.c: Use CHECKING_P instead of ENABLE_CHECKING.
* gengtype.c
disappear during RT libraries build) with valgrind checks on x86_64-linux.
Markus also helped with valgrind test on ppc64le-linux.
Committed as obvious, r228033.
2015-09-23 Mikhail Maltsev <malts...@gmail.com>
PR middle-end/67649
* memory-block.h (memory_block_pool::al
On 09/10/2015 12:07 AM, Jeff Law wrote:
>> On Mon, Aug 31, 2015 at 7:49 AM, Mikhail Maltsev <malts...@gmail.com>
>>> In lra.c we have:
>>>
>>> #ifdef ENABLE_CHECKING
>>>
>>> /* Function checks RTL for correctness. If FINAL_P is true, it
les. Of course right now memory-block
makes much more sense.
>
> I think the patch is ok with the above correctness fix and whatever
> choice you take
> for the bikeshedding. Also fixing Richards review comments, of course.
Fixed.
Bootstrapped and regtested on x86_64-linux and built con
ass_data'
structure. Then 'loops_for_fn' should work.
'selfassign.c' is a good example of a plugin which creates an optimization pass
(and 'dumb_plugin.c' is a good minimal example).
--
Regards,
Mikhail Maltsev
Ping.
On 08/27/2015 09:27 PM, Mikhail Maltsev wrote:
> Hi.
> This patch fixes a rejects-valid bug related to volatile-qualified arguments
> of
> constexpr functions. This is essentially a one-line change in constexpr.c.
> Bootstrapped and regtested on x86_64-pc-linux-gnu. OK for
s on trunk and active development
(feature) branches.
--
Regards,
Mikhail Maltsev
e (i.e. make a list of C++ files with
.c
extension, fix build scripts, run some tests), if it is acceptable.
--
Regards,
Mikhail Maltsev
Ping.
On 08/03/2015 11:40 AM, Mikhail Maltsev wrote:
> On Jul 26, 2015, at 11:50 AM, Andi Kleen <a...@firstfloor.org> wrote:
>> I've been compiling gcc with tcmalloc to do a similar speedup. It would be
>> interesting to compare that to your patch.
> I repeated the test wi
Hi.
This patch fixes a rejects-valid bug related to volatile-qualified arguments of
constexpr functions. This is essentially a one-line change in constexpr.c.
Bootstrapped and regtested on x86_64-pc-linux-gnu. OK for trunk?
gcc/cp/ChangeLog:
2015-08-25 Mikhail Maltsev malts...@gmail.com
On 08/18/2015 10:00 PM, Jeff Law wrote:
On 08/14/2015 10:02 PM, Mikhail Maltsev wrote:
gcc/ChangeLog:
2015-08-15 Mikhail Maltsev malts...@gmail.com
* dominance.c (new_zero_array): Define.
(dom_info): Redefine as class with proper encapsulation.
(dom_info
to pull (same result as
with git push -f).
--
Regards,
Mikhail Maltsev
functions from
virtual-memory.h. Alternatively I could just declare those functions in
coretypes.h. Would that be better?
--
Regards,
Mikhail Maltsev
diff --git a/gcc/Makefile.in b/gcc/Makefile.in
index c1cb4ce..1b4198d 100644
--- a/gcc/Makefile.in
+++ b/gcc/Makefile.in
@@ -1516,7 +1516,7
-07/msg00165.html
Briefly speaking, I noticed that our timers introduce rather significant
measurement errors and proposed some ideas about reducing them. What do you
think?
--
Regards,
Mikhail Maltsev
#include stdio.h
//===- various headers - Existing GCC code
is discarded after we have the dominator tree computed. The
tree itself is stored in et_node-s (which are attached to basic blocks).
dom_info is not used for incremental updates.
gcc/ChangeLog:
2015-08-15 Mikhail Maltsev malts...@gmail.com
* dominance.c (new_zero_array): Define.
(dom_info
, a possible solution is to define a macro which expands to namespace {
during normal build and expands to nothing in some sort of debug build (for
example, when ENABLE_CHECKING is defined).
--
Regards,
Mikhail Maltsev
specifiers (i.e.
struct/enum foo) by simple ones (i.e., just foo) in function prototypes.
Bootstrapped and regtested on x86_64-linux. Tested build of config-list.mk.
gcc/ChangeLog:
2015-08-14 Mikhail Maltsev malts...@gmail.com
* (ENABLE_CHECKING): Define as 0 by default
if
the object size is larger than the block size of the caching pool?
Yes, I though about it, but I hesitated, whether this should be implemented in
advance. I attached the updated patch.
--
Regards,
Mikhail Maltsev
diff --git a/gcc/alloc-pool.c b/gcc/alloc-pool.c
index 7e25915..f8c1351 100644
allocators. Add red zones between allocated
objects when GCC is configured to use ASAN checks.
gcc/ChangeLog:
2015-07-26 Mikhail Maltsev malts...@gmail.com
* alloc-pool.c (memory_block_pool): New class.
(pool_allocator::initialize): Use fixed block size.
(pool_allocator
On 07/17/2015 07:46 PM, Mike Stump wrote:
On Jul 17, 2015, at 2:28 AM, Mikhail Maltsev malts...@gmail.com wrote:
The following code (reduced from wide-int.h) is rejected by Intel C++
Compiler (EDG-based):
So, could you test this with the top of the tree compiler and file a bug
report
and regtested on
x86_64-linux. OK for trunk?
--
Regards,
Mikhail Maltsev
diff --git a/gcc/wide-int.h b/gcc/wide-int.h
index d8f7b46..6e0275f 100644
--- a/gcc/wide-int.h
+++ b/gcc/wide-int.h
@@ -360,21 +360,18 @@ namespace wi
inputs. Note that CONST_PRECISION and VAR_PRECISION cannot
On 07/14/2015 07:38 PM, Marek Polacek wrote:
Ok, in that case I think easiest would the following (I hit the same issue
when writing the -Wtautological-compare patch):
Thanks for taking care of this issue.
--
Regards,
Mikhail Maltsev
13172693 times.
Thoughts?
--
Regards,
Mikhail Maltsev
On 07/10/2015 11:44 PM, Jeff Law wrote:
OK after regression testing.
jeff
Bootstrapped and regtested on x86_64-unknown-linux-gnu. Applied as r225727.
--
Regards,
Mikhail Maltsev
1 - 100 of 170 matches
Mail list logo
