[Bug target/103383] Microblaze bswaphi2 can cause issues with delay slots

2021-12-02 Thread eager at eagercon dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103383

--- Comment #7 from Michael Eager  ---
Do you have a test case which shows the problem?

[Bug target/86772] [meta-bug] tracking port status for CVE-2017-5753

2019-01-27 Thread eager at eagercon dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772

Michael Eager  changed:

   What|Removed |Added

 CC||eager at eagercon dot com

--- Comment #3 from Michael Eager  ---
MicroBlaze does not do speculative execution.  No action needed.

[Bug target/54663] microblaze-linux genchecksum failure: opening microblaze-c.o: No such file or directory

2015-12-14 Thread eager at eagercon dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54663

--- Comment #5 from Michael Eager  ---
(In reply to vries from comment #4)
> A patch was committed for this PR. Can this PR be closed?

Yes.

[Bug bootstrap/61388] [4.8 Regression] linux/microblaze fails to build: undefined machine-specific constraint at this point: Q

2014-06-17 Thread eager at eagercon dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61388

--- Comment #8 from Michael Eager eager at eagercon dot com ---
Thanks.  I've reverted the patch from the gcc-4.8 branch.
Committed revision 211750.


[Bug bootstrap/61388] [4.8 Regression] linux/microblaze fails to build: undefined machine-specific constraint at this point: Q

2014-06-13 Thread eager at eagercon dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61388

--- Comment #3 from Michael Eager eager at eagercon dot com ---
What sources are you building?  

When I build --target=microblaze-xilinx-elf from the current sources, I see the
same warning message for microblaze.md that you list.  I do not see the other
errors.  Constraint Q is defined in constraints.md.


[Bug rtl-optimization/55346] var-tracking generates incomplete/inaccurate debug info

2012-11-19 Thread eager at eagercon dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55346



--- Comment #4 from Michael Eager eager at eagercon dot com 2012-11-19 
21:59:50 UTC ---

Confirmed fixed r193543 (2012-11-15).



gdb-7.5 (top of tree) displays argno correctly; gdb-7.3 does not.


[Bug rtl-optimization/55346] New: var-tracking generates incomplete/inaccurate debug info

2012-11-15 Thread eager at eagercon dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55346



 Bug #: 55346

   Summary: var-tracking generates incomplete/inaccurate debug

info

Classification: Unclassified

   Product: gcc

   Version: 4.8.0

Status: UNCONFIRMED

  Severity: major

  Priority: P3

 Component: rtl-optimization

AssignedTo: unassig...@gcc.gnu.org

ReportedBy: ea...@eagercon.com





Created attachment 28703

  -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=28703

Test program



Var-tracking is does not record the lifetime of variables allocated to

registers correctly, resulting in gdb displaying the variable as optimized

out when it is live.  I've confirmed this problem on x86 and arm.  



The test case is a loop which parses command line options, indexed by integer

variable argno.  When compiled with -g -O2, argno is allocated to rbx, which

is never reused.  The DWARF location list which is generated from

NOTE_INSN_VAR_LOCATION insns, shows disjoint allocations for argno, omitting PC

ranges where the variable is live in rbx.



The DWARF location list has argno as literal 1 beyond the instruction where it

is allocated to rbx.  Argno is defined as rbx starts several instructions after

it is allocated and ends premature.



Var-tracking inserts a NOTE_INSN_VAR_LOCATION for argno as const int 1 at the

start of the BB #2, but one is not inserted when argno is allocated to rbx

later in BB #2.  One is generated later, in BB #5.



Var-tracking inserts a (nil) NOTE_INSN_VAR_LOCATION for argno after BB #3

(branch to epilogue), although argno is live and is used in BB #4, immediately

following BB #3.  Either this should not be generated or another

NOTE_INSN_VAR_LOCATION for argno should be generated at the start of BB #4.


[Bug rtl-optimization/55346] var-tracking generates incomplete/inaccurate debug info

2012-11-15 Thread eager at eagercon dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55346



--- Comment #1 from Michael Eager eager at eagercon dot com 2012-11-15 
19:53:53 UTC ---

Created attachment 28704

  -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=28704

Disassembly and location list


[Bug rtl-optimization/55346] var-tracking generates incomplete/inaccurate debug info

2012-11-15 Thread eager at eagercon dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55346



--- Comment #3 from Michael Eager eager at eagercon dot com 2012-11-15 
22:36:58 UTC ---

Top of tree as of Oct 20, 2012.  I'll update and verify.



On 11/15/2012 01:42 PM, jakub at gcc dot gnu.org wrote:



 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55346



 Jakub Jelinek jakub at gcc dot gnu.org changed:



 What|Removed |Added

 

   CC||jakub at gcc dot gnu.org



 --- Comment #2 from Jakub Jelinek jakub at gcc dot gnu.org 2012-11-15 
 21:42:34 UTC ---

 Which gcc version exactly (svn rev or date) you were using?

 I can't reproduce this on x86_64-linux with current trunk and -g -O2.

   268: Abbrev Number: 4 (DW_TAG_variable)

  69   DW_AT_name: (indirect string, offset: 0x74): argno

  6d   DW_AT_decl_file   : 1

  6e   DW_AT_decl_line   : 4

  6f   DW_AT_type: 0x124

  73   DW_AT_location: 0x98(location list)

 ...

  0098 00400420 00400437 (DW_OP_lit1; 
 DW_OP_stack_value)

  0098 00400437 00400483 (DW_OP_reg3 (rbx))

  0098 00400483 00400488 (DW_OP_breg3 (rbx): -1;

 DW_OP_stack_value)

  0098 00400488 00400491 (DW_OP_reg3 (rbx))

  0098 0040049f 004004cc (DW_OP_reg3 (rbx))

  0098 End of list



 The only gap in there is in between 491 and 49f, and that is the epilogue:

400491:   0f 1f 80 00 00 00 00nopl   0x0(%rax)

400498:   5b  pop%rbx

400499:   5d  pop%rbp

40049a:   31 c0   xor%eax,%eax

40049c:   41 5c   pop%r12

40049e:   c3  retq

40049f:   90  nop



 I can reproduce it with r192900 though, so I bet this is a dup of PR54693

 (which after all was your testcase).




[Bug target/54663] microblaze-linux genchecksum failure: opening microblaze-c.o: No such file or directory

2012-10-23 Thread eager at eagercon dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54663



--- Comment #1 from Michael Eager eager at eagercon dot com 2012-10-23 
15:09:18 UTC ---

Not able to reproduce.  GCC HEAD builds for microblaze without known problem. 



Not enough info in report to reproduce or identify problem.



If there was a problem compiling microblaze-c.o, it would be logged before the

ar to create libbackend.a.


[Bug testsuite/45856] gcc.c-torture/execute/cmpsf-1.c/cmpsi-2.c failed on x86-64

2010-10-12 Thread eager at eagercon dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45856

--- Comment #12 from Michael Eager eager at eagercon dot com 2010-10-12 
20:07:13 UTC ---
Patches checked in.


[Bug testsuite/45856] gcc.c-torture/execute/cmpsf-1.c/cmpsi-2.c failed on x86-64

2010-10-06 Thread eager at eagercon dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45856

--- Comment #7 from Michael Eager eager at eagercon dot com 2010-10-06 
18:58:15 UTC ---
Attached patches should correct test case failures.  Tested on x86_64 and x86.


[Bug target/32889] [4.2 Regression] ICE in delete_output_reload, at reload1.c:7926

2008-02-23 Thread eager at eagercon dot com


--- Comment #16 from eager at eagercon dot com  2008-02-23 21:18 ---
Attached is a patch to reload.c which addresses the root cause.


-- 

eager at eagercon dot com changed:

   What|Removed |Added

 CC||eager at eagercon dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32889



[Bug target/32889] [4.2 Regression] ICE in delete_output_reload, at reload1.c:7926

2008-02-23 Thread eager at eagercon dot com


--- Comment #17 from eager at eagercon dot com  2008-02-23 21:21 ---
Created an attachment (id=15215)
 -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15215action=view)
Fix to reload.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32889



[Bug middle-end/34762] [4.2 regression] internal compiler error: in delete_output_reload, at reload1.c:7958

2008-02-23 Thread eager at eagercon dot com


--- Comment #10 from eager at eagercon dot com  2008-02-23 21:24 ---
Created an attachment (id=15216)
 -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15216action=view)
More complete fix for reload.c

This is a more complete patch to reload.c.
Duplicate of fix for bug 32889.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34762



[Bug other/28596] New: libssp does not build for cross-compile

2006-08-03 Thread eager at eagercon dot com
Configure for libssp tries to build or run executables, even when configured
for cross-compile.  

Workaround: specify --disable-libssp in configure.


-- 
   Summary: libssp does not build for cross-compile
   Product: gcc
   Version: 4.1.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: eager at eagercon dot com
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: powerpc-unknown-eabi


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28596