On Oct 1, 2012, at 2:51 PM, Richard Sandiford wrote:
> ...
> E.g. for MIPS, SImode loads and stores have a displacement range of
> [-32768, 32764], but DImode loads and stores only accept [-32768, 32760].
> So the maximal displacement depends on mode, even though the instruction set
> is pretty r
Ping ^ 2...
--
If the only reference in a source file is to a static method of a class, then
GCC would output debug information for the class name but not any of its
members or base classes. The attached patch fixes this by having
"prune_unused_types_mark" mark all of the parent's childre
On Oct 4, 2012, at 1:38 PM, Cary Coutant wrote:
>> /* We also have to mark its parents as used.
>> -(But we don't want to mark our parents' kids due to this.) */
>> +(But we don't want to mark our parent's kids due to this,
>> +unless it is a class.) */
>> if (
On Oct 4, 2012, at 2:58 PM, Jakub Jelinek wrote:
> On Thu, Oct 04, 2012 at 06:32:20PM +, paul_kon...@dell.com wrote:
>> --- testsuite/g++.dg/debug/dwarf2/pr54508.C (revision 0)
>> +++ testsuite/g++.dg/debug/dwarf2/pr54508.C (revision 0)
>> @@ -0,0 +1,67 @@
>> +// PR debug/54508
>> +// { dg-
On Oct 4, 2012, at 12:09 PM,
wrote:
> Ping ^ 2...
>
> --
>
> If the only reference in a source file is to a static method of a class, then
> GCC would output debug information for the class name but not any of its
> members or base classes. The attached patch fixes this by having
> "
Updated patch: there were two existing testcases that needed to be adjusted
because of this fix.
Ran check RUNTESTFLAGS=dwarf2.exp, no regressions.
paul
ChangeLog:
2012-10-04 Paul Koning
* dwarf2out.c (prune_unused_types_mark): Mark all of parent's
children if paren
On Oct 4, 2012, at 8:26 PM, Cary Coutant wrote:
>> Index: gcc/testsuite/g++.dg/debug/dwarf2/localclass1.C
>> ===
>> --- gcc/testsuite/g++.dg/debug/dwarf2/localclass1.C (revision 192048)
>> +++ gcc/testsuite/g++.dg/debug/dwarf2/lo
On Oct 4, 2012, at 8:26 PM, Cary Coutant wrote:
>> Index: gcc/testsuite/g++.dg/debug/dwarf2/localclass1.C
>> ===
>> --- gcc/testsuite/g++.dg/debug/dwarf2/localclass1.C (revision 192048)
>> +++ gcc/testsuite/g++.dg/debug/dwarf2/lo
On Oct 5, 2012, at 4:16 AM, Jakub Jelinek wrote:
> On Thu, Oct 04, 2012 at 05:26:11PM -0700, Cary Coutant wrote:
>>> Index: gcc/testsuite/g++.dg/debug/dwarf2/localclass1.C
>>> ===
>>> --- gcc/testsuite/g++.dg/debug/dwarf2/localclass1
On Oct 5, 2012, at 11:34 AM,
wrote:
>
> On Oct 5, 2012, at 4:16 AM, Jakub Jelinek wrote:
>
>> On Thu, Oct 04, 2012 at 05:26:11PM -0700, Cary Coutant wrote:
Index: gcc/testsuite/g++.dg/debug/dwarf2/localclass1.C
===
>>>
On Oct 5, 2012, at 2:43 PM, Cary Coutant wrote:
>>> It seems to me that there are cases where we just want to emit the
>>> class for the context info (like a namespace, which doesn't have to be
>>> complete everywhere). Is there a way to tell the debugger that this
>>> class declaration is incomp
On Oct 5, 2012, at 2:43 PM, Cary Coutant wrote:
>>> It seems to me that there are cases where we just want to emit the
>>> class for the context info (like a namespace, which doesn't have to be
>>> complete everywhere). Is there a way to tell the debugger that this
>>> class declaration is incomp
On Oct 5, 2012, at 6:05 PM, Cary Coutant wrote:
>> There certainly is a fair amount of code in dwarf2read.c in gdb to handle
>> DW_AT_declaration and do things differently for declarations.
>>
>> Should I rework this patch to use that mechanism instead? If so, how? If
>> the class is marked
On Oct 5, 2012, at 6:05 PM, Cary Coutant wrote:
>> There certainly is a fair amount of code in dwarf2read.c in gdb to handle
>> DW_AT_declaration and do things differently for declarations.
>>
>> Should I rework this patch to use that mechanism instead? If so, how? If
>> the class is marked
On Oct 23, 2012, at 2:02 PM, Jason Merrill wrote:
> OK.
>
> Jason
Thanks. Committed.
paul
On Dec 10, 2013, at 9:50 AM, Kirill Yukhin wrote:
> Hello,
> On 09 Dec 14:08, H.J. Lu wrote:
>> There are no regressions on Linux/x86-64 with -m32 and -m64.
>> Can you check if it improves code quality on x886?
>
> That is exactly what I was talking about. However I wasn't sure
> that we can ch
On Dec 10, 2013, at 2:12 PM, H.J. Lu wrote:
> On Tue, Dec 10, 2013 at 11:05 AM, Tejas Belagod wrote:
>> ...
>> So, if (subreg:DI (match_operand:V4SF 1 "register_operand" "x,x") 0) is a
>> valid subreg, why not allow it in CANNOT_CHANGE_MODE_CLASS (like in Kirill's
>> patch http://gcc.gnu.org/ml
On Nov 22, 2013, at 3:43 AM, Richard Sandiford
wrote:
> genrecog does some useful sanity checks on the .md files. At the moment
> it only reports most of the problems as warnings though, which means you
> won't notice them unless you specifically look.
>
> I think the only message in validate
On Jun 12, 2014, at 3:24 PM, Segher Boessenkool
wrote:
> On Thu, Jun 05, 2014 at 10:43:25PM +0100, Richard Sandiford wrote:
>> This final patch uses a common .md file to define all standard
>> constraints except 'g'.
>
> I had a look at what targets still use "g". Note: there can be
> errors
From: gcc-patches-ow...@gcc.gnu.org [gcc-patches-ow...@gcc.gnu.org] on behalf
of H.J. Lu [hjl.to...@gmail.com]
Sent: Tuesday, May 19, 2015 11:27 AM
To: Joseph Myers
Cc: Magnus Granberg; GCC Patches
Subject: Re: PING^3: [PATCH]: New configure options that m
> On Apr 22, 2016, at 12:21 PM, Bernd Schmidt wrote:
>
> (Apologies if you get this twice, the mailing list didn't like the html
> attachment in the first attempt).
>
> We frequently get malformatted patches, and it's been brought to my attention
> that some people don't even make the effort
On Sep 11, 2014, at 9:22 PM, Joseph S. Myers wrote:
> This patch removes the LIBGCC2_HAS_{SF,DF,XF,TF}_MODE target macros,
> replacing them by predefines with -fbuilding-libgcc, together with a
> target hook that can influence those predefines when needed.
>
> The new default is that a floating
>There is no real post morten debugging on AVR as there is nothing like core
>dump.
But if there is any kind of debugging at all, you might use the debugger to put
a breakpoint in abort(), and if so, having that invoked via jmp means you don't
know who called it. So you'd want a way to suppres
Currently the description of -feliminate-unused-debug-types says that it is off
by default. In fact, it is on by default. The attached patch corrects the
documentation to reflect that.
Ok to commit?
paul
2012-09-17 Paul Koning
* doc/invoke.text (-feliminate-unused-debug-t
On Sep 17, 2012, at 1:20 PM, Ian Lance Taylor wrote:
> On Mon, Sep 17, 2012 at 8:59 AM, wrote:
>>
>> 2012-09-17 Paul Koning
>>
>>* doc/invoke.text (-feliminate-unused-debug-types): Update to
>>reflect that this is enabled by default.
>
> This is OK.
>
> Thanks.
>
> Ian
If the only reference in a source file is to a static method of a class, then
GCC would output debug information for the class name but not any of its
members or base classes. The attached patch fixes this by having
"prune_unused_types_mark" mark all of the parent's children if the parent DIE
Attached below is an update to the testcase file, to fix the scan-assembler
regexp comment character matching. This uses the same regexp element that H-P
Nilsson used in the fix to nested-3.C two days ago.
By the way, I ran check-g++ for dwarf2.exp on this change, no regressions.
Ok to commit?
Ping...
paul
Begin forwarded message:
> From:
> Date: September 20, 2012 4:55:05 PM EDT
> To:
> Subject: Re: [patch] pr/54508: fix incomplete debug information for class
>
> Attached below is an update to the testcase file, to fix the scan-assembler
> regexp comment character matchin
On Sep 27, 2012, at 2:04 PM, Uros Bizjak wrote:
>
>
>
> I agree (subreg:M (op:N A C) 0) to (op:M (subreg:N (A 0)) C) is
> a good transformation, but why do we need to handle as special
> the case where the subreg is itself the operand of a plus or minus?
> I think it should hap
It turns out that there is a second target that doesn't define
ASM_OUTPUT_ADDR_DIFF_ELT: pdp11. I'll fix that.
The documentation is out of date as a consequence of this patch, because it
still says that ASM_OUTPUT_ADDR_DIFF_ELT is optional which is no longer the
case (or not unless you take so
On May 16, 2012, at 1:27 PM,
wrote:
> It turns out that there is a second target that doesn't define
> ASM_OUTPUT_ADDR_DIFF_ELT: pdp11. I'll fix that.
>
> The documentation is out of date as a consequence of this patch, because it
> still says that ASM_OUTPUT_ADDR_DIFF_ELT is optional whic
> I am checking in the patch below to the mainline and 4.6 branch. It
> disables the peephole optimizations in the rx.md file that combine a
> load followed by a zero- or sign- extend operation. The disabling
> only happens at -O3 (or higher) as although the peepholes reduce the
> number of
>> You should have a way to turn this off. Otherwise this makes
>> debugging the call to abort impossible.
>
>What do you propose?
>
>o A command line option that is on per default like
> -mnoreturn-tail-calls or -mjmp-noreturn
>
>o Hard-coded factor out some function names like "abort",
> "exi
These look fine. I'll defer to others on whether it should wait to Phase 1.
I had tried to make divmod work but never figured out the reason why it did
not. Thanks for answering that question.
As for the subregs that Richard commented on -- I will gladly admit that this
target isn't all clean
By the way, the "compile" subset of the testsuite works for pdp11; it has some
errors which still need cleanup but a large fraction works.
paul
-Original Message-
From: Steven Bosscher [mailto:stevenb@gmail.com]
Sent: Tuesday, February 14, 2012 5:09 PM
To: Koning, Paul; GCC
35 matches
Mail list logo
