[Bug c/58256] gcc for h8300 internal compiler error: in maybe_record_trace_start

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58256 --- Comment #12 from Chen Gang gang.chen at asianux dot com --- I am just comparing the issue code demo and the other 3 correct code demo (the demostrations which del one param, or add one param, or add two params are all correct). I find

[Bug c/58256] gcc for h8300 internal compiler error: in maybe_record_trace_start

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58256 --- Comment #10 from Chen Gang gang.chen at asianux dot com --- Created attachment 30826 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30826action=edit (sorry, it is cc1 issue) It is the related command line for cc1 and the summary work flow

[Bug c/58256] gcc for h8300 internal compiler error: in maybe_record_trace_start

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58256 --- Comment #11 from Chen Gang gang.chen at asianux dot com --- It seems, I am really really a newbie !! 1. after append -gstabs+, can let gdb work well. 2. can use the internal dump_file (dump_start/dump_end) to analyze all information

[Bug c/58256] gcc for h8300 internal compiler error: in maybe_record_trace_start

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58256 --- Comment #8 from Chen Gang gang.chen at asianux dot com --- For gcc-4.9.0, I got summary trace for it (call stack for cc1, how many the related loopings during calling flow), hope it may be a little useful. (I will do the same thing for gcc

[Bug c/58256] gcc for h8300 internal compiler error: in maybe_record_trace_start

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58256 --- Comment #9 from Chen Gang gang.chen at asianux dot com --- Created attachment 30825 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30825action=edit Issue is within xgcc, can exclude cc1 by comparing the summary log between gcc-4.8.0

[Bug c/58256] gcc for h8300 internal compiler error: in maybe_record_trace_start

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58256 --- Comment #7 from Chen Gang gang.chen at asianux dot com --- Created attachment 30821 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30821action=edit some simple modification based on the reduced .c file. After learning from what you have

[Bug c/58401] gcc for h8300 internal compiler error: insn does not satisfy its constraints at fs/ocfs2/dlm/dlmdomain.c: In function 'dlm_query_join_handler'

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58401 --- Comment #4 from Chen Gang gang.chen at asianux dot com --- Created attachment 30810 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30810action=edit the .i file for fs/ocfs2/dlm/dlmdomain.c (bzip2 compressed) I put the related .i files

[Bug c/58401] gcc for h8300 internal compiler error: insn does not satisfy its constraints at fs/ocfs2/dlm/dlmdomain.c: In function 'dlm_query_join_handler'

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58401 --- Comment #5 from Chen Gang gang.chen at asianux dot com --- Created attachment 30811 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30811action=edit the .i file for fs/ocfs2/dlm/dlmrecovery.c (bzip2 compressed)

[Bug c/58400] gcc for h8300 internal compiler error: insn does not satisfy its constraints at fs/ext4/mballoc.c: In function 'mb_free_blocks':

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58400 --- Comment #4 from Chen Gang gang.chen at asianux dot com --- Created attachment 30812 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30812action=edit the .i file for fs/ext4/mballoc.c (bzip2 compressed) I put .i file in attachment which

[Bug c/58256] gcc for h8300 internal compiler error: in maybe_record_trace_start

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58256 --- Comment #5 from Chen Gang gang.chen at asianux dot com --- Created attachment 30813 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30813action=edit the .i file for fs/namei.c (bzip2 compressed) I put .i file for fs/namei.c which need

[Bug c/58256] gcc for h8300 internal compiler error: in maybe_record_trace_start

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58256 --- Comment #1 from Chen Gang gang.chen at asianux dot com --- It is for Linux kernel next-20130828 version. and for the latest Linux kernel, h8/300 has been removed.

[Bug c/58256] gcc for h8300 internal compiler error: in maybe_record_trace_start

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58256 --- Comment #2 from Chen Gang gang.chen at asianux dot com --- it is not found in gcc-4.8.0.

[Bug c/58256] gcc for h8300 internal compiler error: in maybe_record_trace_start

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58256 --- Comment #3 from Chen Gang gang.chen at asianux dot com --- The related command line: /usr/local/bin/h8300-gchen-elf-gcc -Wp,-MD,fs/.namei.o.d -nostdinc -isystem /usr/local/lib/gcc/h8300-gchen-elf/4.9.0/include -I/root/linux-next/arch

[Bug c/58256] gcc for h8300 internal compiler error: in maybe_record_trace_start

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58256 Chen Gang gang.chen at asianux dot com changed: What|Removed |Added CC||gang.chen

[Bug c/58400] New: gcc for h8300 internal compiler error: insn does not satisfy its constraints at fs/ext4/mballoc.c: In function 'mb_free_blocks':

Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gang.chen at asianux dot com For Linux kernel next-20130828 version: The command line: /usr/local/bin

[Bug c/58400] gcc for h8300 internal compiler error: insn does not satisfy its constraints at fs/ext4/mballoc.c: In function 'mb_free_blocks':

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58400 --- Comment #1 from Chen Gang gang.chen at asianux dot com --- fs/ext4/mballoc.c:1459:1: internal compiler error: in reload_cse_simplify_operands, at postreload.c:411 0x8e0a95 _fatal_insn(char const*, rtx_def const*, char const*, int, char const

[Bug c/58400] gcc for h8300 internal compiler error: insn does not satisfy its constraints at fs/ext4/mballoc.c: In function 'mb_free_blocks':

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58400 --- Comment #2 from Chen Gang gang.chen at asianux dot com --- For gcc-4.8.0 and gcc-4.7.4, it has this issue too.

[Bug c/58400] gcc for h8300 internal compiler error: insn does not satisfy its constraints at fs/ext4/mballoc.c: In function 'mb_free_blocks':

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58400 --- Comment #3 from Chen Gang gang.chen at asianux dot com --- If no opitimization (without -Os), it will be OK.

[Bug c/58401] New: gcc for h8300 internal compiler error: insn does not satisfy its constraints at fs/ocfs2/dlm/dlmdomain.c: In function 'dlm_query_join_handler'

' Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gang.chen at asianux dot com For Linux kernel next-20130828 version The related command

[Bug c/58401] gcc for h8300 internal compiler error: insn does not satisfy its constraints at fs/ocfs2/dlm/dlmdomain.c: In function 'dlm_query_join_handler'

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58401 Chen Gang gang.chen at asianux dot com changed: What|Removed |Added CC||gang.chen

[Bug c/58401] gcc for h8300 internal compiler error: insn does not satisfy its constraints at fs/ocfs2/dlm/dlmdomain.c: In function 'dlm_query_join_handler'

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58401 --- Comment #2 from Chen Gang gang.chen at asianux dot com --- Alos for fs/ocfs2/dlm/dlmrecovery.c /usr/local/bin/h8300-gchen-elf-gcc -Wp,-MD,fs/ocfs2/dlm/.dlmrecovery.o.d -nostdinc -isystem /usr/local/lib/gcc/h8300-gchen-elf/4.9.0/include -I

[Bug c/58401] gcc for h8300 internal compiler error: insn does not satisfy its constraints at fs/ocfs2/dlm/dlmdomain.c: In function 'dlm_query_join_handler'

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58401 --- Comment #3 from Chen Gang gang.chen at asianux dot com --- It has too many same issues (maybe they are duplicating), if necessary, I will list them too (non-reply means not need list them).

[Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start

Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gang.chen at asianux dot com [root@dhcp122 linux-next]# /usr/local/bin/h8300-gchen-elf-gcc -v Using built-in specs. COLLECT_GCC=/usr/local/bin/h8300-gchen-elf-gcc COLLECT_LTO_WRAPPER=/usr

[Bug middle-end/57856] for an uninitialized variable, gcc assumes it already has value instead of report uninitialized warnings.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57856 Chen Gang gang.chen at asianux dot com changed: What|Removed |Added Resolution|DUPLICATE |FIXED

[Bug tree-optimization/18501] [4.7/4.8/4.9 Regression] Missing 'used uninitialized' warning (CCP)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18501 --- Comment #64 from Chen Gang gang.chen at asianux dot com --- (In reply to Manuel López-Ibáñez) Firstly, thank you very much for keeping tracing this bug almost 10 years, and provided your suggestions as much as possible. What you have done

[Bug c/57856] New: for an uninitialized variable, gcc assumes it already has value instead of report uninitialized warnings.

: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gang.chen at asianux dot com Created attachment 30477 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30477action=edit Related disassemble code

[Bug middle-end/57856] for an uninitialized variable, gcc assumes it already has value instead of report uninitialized warnings.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57856 Chen Gang gang.chen at asianux dot com changed: What|Removed |Added CC||gang.chen

[Bug middle-end/57856] for an uninitialized variable, gcc assumes it already has value instead of report uninitialized warnings.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57856 --- Comment #3 from Chen Gang gang.chen at asianux dot com --- Created attachment 30479 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30479action=edit The related warnings, not find uninitailized warning for lru.

[Bug middle-end/57856] for an uninitialized variable, gcc assumes it already has value instead of report uninitialized warnings.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57856 --- Comment #4 from Chen Gang gang.chen at asianux dot com --- Created attachment 30480 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30480action=edit This attachment is for gcc 4.9.0 from compiling source code (sorry, the original

[Bug middle-end/57856] for an uninitialized variable, gcc assumes it already has value instead of report uninitialized warnings.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57856 --- Comment #5 from Chen Gang gang.chen at asianux dot com --- (In reply to Andrew Pinski from comment #1) I think this is a dup of another bug. Firstly, thank you reply as soon as possible. Could you provide the related Bug number ? Thanks.