public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/58256] New: gcc for h8300  internal compiler error: in maybe_record_trace_start
@ 2013-08-28  3:22 gang.chen at asianux dot com
  2013-09-12  3:34 ` [Bug c/58256] " gang.chen at asianux dot com
                   ` (12 more replies)
  0 siblings, 13 replies; 14+ messages in thread
From: gang.chen at asianux dot com @ 2013-08-28  3:22 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 58256
           Summary: gcc for h8300  internal compiler error: in
                    maybe_record_trace_start
           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

[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/local/libexec/gcc/h8300-gchen-elf/4.9.0/lto-wrapper
Target: h8300-gchen-elf
Configured with: ../gcc-4.9.0/configure --target=h8300-gchen-elf
--without-header --disable-nls --enable-language=c --disable-threads
--disable-shared --enable-werror=no
Thread model: single
gcc version 4.9.0 20130827 (experimental) (GCC)


In file included from include/linux/thread_info.h:11:0,
                 from include/linux/preempt.h:9,
                 from include/linux/spinlock.h:50,
                 from include/linux/mmzone.h:7,
                 from include/linux/gfp.h:4,
                 from include/linux/slab.h:12,
                 from fs/namei.c:20:
fs/namei.c: In function 'SyS_mknodat':
include/linux/bug.h:33:45: internal compiler error: in
maybe_record_trace_start, at dwarf2cfi.c:2217
 #define BUILD_BUG_ON_ZERO(e) (sizeof(struct { int:-!!(e); }))
                                             ^
include/linux/syscalls.h:104:31: note: in expansion of macro
'BUILD_BUG_ON_ZERO'
 #define __SC_TEST(t, a) (void)BUILD_BUG_ON_ZERO(!__TYPE_IS_LL(t) && sizeof(t)
> sizeof(long))
                               ^
include/linux/syscalls.h:91:23: note: in expansion of macro '__SC_TEST'
 #define __MAP1(m,t,a) m(t,a)
                       ^
include/linux/syscalls.h:92:35: note: in expansion of macro '__MAP1'
 #define __MAP2(m,t,a,...) m(t,a), __MAP1(m,__VA_ARGS__)
                                   ^
include/linux/syscalls.h:93:35: note: in expansion of macro '__MAP2'
 #define __MAP3(m,t,a,...) m(t,a), __MAP2(m,__VA_ARGS__)
                                   ^
include/linux/syscalls.h:94:35: note: in expansion of macro '__MAP3'
 #define __MAP4(m,t,a,...) m(t,a), __MAP3(m,__VA_ARGS__)
                                   ^
include/linux/syscalls.h:97:22: note: in expansion of macro '__MAP4'
 #define __MAP(n,...) __MAP##n(__VA_ARGS__)
                      ^
include/linux/syscalls.h:194:3: note: in expansion of macro '__MAP'
   __MAP(x,__SC_TEST,__VA_ARGS__);    \
   ^
include/linux/syscalls.h:183:2: note: in expansion of macro '__SYSCALL_DEFINEx'
  __SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
  ^
include/linux/syscalls.h:177:36: note: in expansion of macro 'SYSCALL_DEFINEx'
 #define SYSCALL_DEFINE4(name, ...) SYSCALL_DEFINEx(4, _##name, __VA_ARGS__)
                                    ^
fs/namei.c:3209:1: note: in expansion of macro 'SYSCALL_DEFINE4'
 SYSCALL_DEFINE4(mknodat, int, dfd, const char __user *, filename, umode_t,
mode,
 ^
0x68949a maybe_record_trace_start
        ../../gcc-4.9.0/gcc/dwarf2cfi.c:2217
0x689739 create_trace_edges
        ../../gcc-4.9.0/gcc/dwarf2cfi.c:2309
0x68981c scan_trace
        ../../gcc-4.9.0/gcc/dwarf2cfi.c:2522
0x68a29e create_cfi_notes
        ../../gcc-4.9.0/gcc/dwarf2cfi.c:2548
0x68a29e execute_dwarf2_frame
        ../../gcc-4.9.0/gcc/dwarf2cfi.c:2903
0x68a29e execute
        ../../gcc-4.9.0/gcc/dwarf2cfi.c:3399
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[1]: *** [fs/namei.o] Error 1
make: *** [fs] Error 2


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Bug c/58256] gcc for h8300  internal compiler error: in maybe_record_trace_start
  2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
@ 2013-09-12  3:34 ` gang.chen at asianux dot com
  2013-09-12  3:36 ` gang.chen at asianux dot com
                   ` (11 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: gang.chen at asianux dot com @ 2013-09-12  3:34 UTC (permalink / raw)
  To: gcc-bugs

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.


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Bug c/58256] gcc for h8300  internal compiler error: in maybe_record_trace_start
  2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
  2013-09-12  3:34 ` [Bug c/58256] " gang.chen at asianux dot com
@ 2013-09-12  3:36 ` gang.chen at asianux dot com
  2013-09-12  3:44 ` gang.chen at asianux dot com
                   ` (10 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: gang.chen at asianux dot com @ 2013-09-12  3:36 UTC (permalink / raw)
  To: gcc-bugs

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.


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Bug c/58256] gcc for h8300  internal compiler error: in maybe_record_trace_start
  2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
  2013-09-12  3:34 ` [Bug c/58256] " gang.chen at asianux dot com
  2013-09-12  3:36 ` gang.chen at asianux dot com
@ 2013-09-12  3:44 ` gang.chen at asianux dot com
  2013-09-12  3:45 ` gang.chen at asianux dot com
                   ` (9 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: gang.chen at asianux dot com @ 2013-09-12  3:44 UTC (permalink / raw)
  To: gcc-bugs

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/h8300/include -Iarch/h8300/include/generated  -Iinclude
-I/root/linux-next/arch/h8300/include/uapi -Iarch/h8300/include/generated/uapi
-I/root/linux-next/include/uapi -Iinclude/generated/uapi -include
/root/linux-next/include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common
-Werror-implicit-function-declaration -Wno-format-security
-fno-delete-null-pointer-checks -Os -Wno-maybe-uninitialized -mh -mint32
-fno-builtin -g -D__linux__ -DUTS_SYSNAME=\"uClinux\" -fno-reorder-blocks
-fno-ipa-cp-clone -fno-partial-inlining -Wframe-larger-than=1024
-fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer -g
-femit-struct-debug-baseonly -fno-var-tracking
-fno-inline-functions-called-once -Wdeclaration-after-statement
-Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int
-Werror=strict-prototypes -DCC_HAVE_ASM_GOTO     -D"KBUILD_STR(s)=#s"
-D"KBUILD_BASENAME=KBUILD_STR(namei)"  -D"KBUILD_MODNAME=KBUILD_STR(namei)" -c
-o fs/.tmp_namei.o fs/namei.c


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Bug c/58256] gcc for h8300  internal compiler error: in maybe_record_trace_start
  2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
                   ` (2 preceding siblings ...)
  2013-09-12  3:44 ` gang.chen at asianux dot com
@ 2013-09-12  3:45 ` gang.chen at asianux dot com
  2013-09-13  3:14 ` gang.chen at asianux dot com
                   ` (8 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: gang.chen at asianux dot com @ 2013-09-12  3:45 UTC (permalink / raw)
  To: gcc-bugs

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 at asianux dot com

--- Comment #4 from Chen Gang <gang.chen at asianux dot com> ---
(In reply to Chen Gang from comment #2)
> it is not found in gcc-4.8.0.

That means: gcc-4.8.0 has no this issue, only 4.9.0 has (and in my memory,
gcc-4.7.4 may also has this issue, but I am not quite sure).


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Bug c/58256] gcc for h8300  internal compiler error: in maybe_record_trace_start
  2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
                   ` (3 preceding siblings ...)
  2013-09-12  3:45 ` gang.chen at asianux dot com
@ 2013-09-13  3:14 ` gang.chen at asianux dot com
  2013-09-13 21:20 ` law at redhat dot com
                   ` (7 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: gang.chen at asianux dot com @ 2013-09-13  3:14 UTC (permalink / raw)
  To: gcc-bugs

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=30813&action=edit
the .i file for fs/namei.c (bzip2 compressed)

I put .i file for fs/namei.c which need "bzip2 -d" to decompress.


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Bug c/58256] gcc for h8300  internal compiler error: in maybe_record_trace_start
  2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
                   ` (4 preceding siblings ...)
  2013-09-13  3:14 ` gang.chen at asianux dot com
@ 2013-09-13 21:20 ` law at redhat dot com
  2013-09-14 16:47 ` gang.chen at asianux dot com
                   ` (6 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: law at redhat dot com @ 2013-09-13 21:20 UTC (permalink / raw)
  To: gcc-bugs

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

Jeffrey A. Law <law at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-09-13
                 CC|                            |ccoutant at google dot com,
                   |                            |jason at redhat dot com,
                   |                            |law at redhat dot com
     Ever confirmed|0                           |1

--- Comment #6 from Jeffrey A. Law <law at redhat dot com> ---
Reduced testcase.  Appears to be blowing up in the dwarf2 bits.

Compile with -Os -mint32 -mh -fomit-frame-pointer -g

typedef _Bool bool;
typedef unsigned short umode_t;
enum {
 false = 0,
 true = 1
};
struct dentry {
 struct inode *d_inode;
};
struct path {
 struct dentry *dentry;
};
extern int vfs_create(struct inode *, struct dentry *, umode_t, bool);


long SYSC_mknodat(int dfd, const char * filename, umode_t mode, unsigned dev)
{
 struct dentry *dentry;
 struct path path;
 int error;
 unsigned int lookup_flags = 0;
 switch (mode & 00170000) {
  case 0: case 0100000:
   error = vfs_create(path.dentry->d_inode,dentry,mode,true);
   break;
  case 0020000: case 0060000:
   error = vfs_mknod(path.dentry->d_inode,dentry,mode, new_decode_dev(dev));
   break;
 }
}


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Bug c/58256] gcc for h8300  internal compiler error: in maybe_record_trace_start
  2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
                   ` (5 preceding siblings ...)
  2013-09-13 21:20 ` law at redhat dot com
@ 2013-09-14 16:47 ` gang.chen at asianux dot com
  2013-09-15 12:27 ` gang.chen at asianux dot com
                   ` (5 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: gang.chen at asianux dot com @ 2013-09-14 16:47 UTC (permalink / raw)
  To: gcc-bugs

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=30821&action=edit
some simple modification based on the reduced .c file.

After learning from what you have done, and give a little additional trying, it
seems we can focus on the new_devcode_dev().

  If it is not defined or defined as a simple inline function, can cause issue.

  If use normal parameter (not inline function), it will be OK.

  If add/del one parameter before new_devcode_dev(), it also be OK.

Please check the attachment for details.


Hmm... next, is it a suitable/correct way to debug gcc-4.9.0 (can cause issue)
and gcc-4.8.0 (no issue) for it with gdb, and comparing them? (I am just trying
in this way)

Thanks.


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Bug c/58256] gcc for h8300  internal compiler error: in maybe_record_trace_start
  2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
                   ` (6 preceding siblings ...)
  2013-09-14 16:47 ` gang.chen at asianux dot com
@ 2013-09-15 12:27 ` gang.chen at asianux dot com
  2013-09-16  4:37 ` gang.chen at asianux dot com
                   ` (4 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: gang.chen at asianux dot com @ 2013-09-15 12:27 UTC (permalink / raw)
  To: gcc-bugs

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-4.8.0, and compare them).

And it seems: gdb can not print the variables' value when "g++ -g -Wall
-static-libstdc++ -static-libgcc" which is effect with cc1 and xgcc.

If can let gdb print the vaiables' value, life will be a little easier (don't
need dump the related variables' values mannually).

Welcome any additional suggestions or completions.

(gdb) bt
#0  maybe_record_trace_start(rtx_def*, rtx_def*) () at
../../gcc-4.9.0/gcc/dwarf2cfi.c:2184
#1  0x00000000006da82b in scan_trace(dw_trace_info*) () at
../../gcc-4.9.0/gcc/dwarf2cfi.c:2399
#2  0x00000000006dadeb in create_cfi_notes() () at
../../gcc-4.9.0/gcc/dwarf2cfi.c:2557
#3  0x00000000006db8e5 in execute_dwarf2_frame() () at
../../gcc-4.9.0/gcc/dwarf2cfi.c:2912
#4  0x00000000006dc5e3 in (anonymous namespace)::pass_dwarf2_frame::execute()
() at ../../gcc-4.9.0/gcc/dwarf2cfi.c:3408
#5  0x0000000000989d20 in execute_one_pass(opt_pass*) () at
../../gcc-4.9.0/gcc/passes.c:2201
#6  0x0000000000989f41 in execute_pass_list(opt_pass*) () at
../../gcc-4.9.0/gcc/passes.c:2257
#7  0x0000000000989f72 in execute_pass_list(opt_pass*) () at
../../gcc-4.9.0/gcc/passes.c:2258
#8  0x0000000000989f72 in execute_pass_list(opt_pass*) () at
../../gcc-4.9.0/gcc/passes.c:2258
#9  0x000000000068cbbd in expand_function(cgraph_node*) () at
../../gcc-4.9.0/gcc/cgraphunit.c:1723
#10 0x000000000068d085 in expand_all_functions() () at
../../gcc-4.9.0/gcc/cgraphunit.c:1828
#11 0x000000000068d9e9 in compile() () at ../../gcc-4.9.0/gcc/cgraphunit.c:2165
#12 0x000000000068db62 in finalize_compilation_unit() () at
../../gcc-4.9.0/gcc/cgraphunit.c:2242
#13 0x00000000005225ac in c_write_global_declarations() () at
../../gcc-4.9.0/gcc/c/c-decl.c:10125
#14 0x0000000000a4c25b in compile_file() () at ../../gcc-4.9.0/gcc/toplev.c:560
#15 0x0000000000a4e22e in do_compile() () at ../../gcc-4.9.0/gcc/toplev.c:1891
#16 0x0000000000a4e3a3 in toplev_main(int, char**) () at
../../gcc-4.9.0/gcc/toplev.c:1969
#17 0x0000000000e5b390 in main ()


(gdb) r -Os -mint32 -mh -fomit-frame-pointer -g /tmp/ana/namei/namei.c
Starting program: /android/src/build-gcc-h8300g/gcc/xgcc -Os -mint32 -mh
-fomit-frame-pointer -g /tmp/ana/namei/namei.c

gchen_tag: progname: xgcc, string: cc1

Detaching after fork from child process 8965.

gchen_tag: execute_pass_list: level: 1, count: 0.

gchen_tag: execute_pass_list: level: 1, count: 1.

gchen_tag: execute_pass_list: level: 1, count: 2.

gchen_tag: execute_pass_list: level: 1, count: 3.

gchen_tag: execute_pass_list: level: 1, count: 4.

gchen_tag: execute_pass_list: level: 1, count: 5.

gchen_tag: execute_pass_list: level: 1, count: 6.

gchen_tag: execute_pass_list: level: 1, count: 7.

gchen_tag: execute_pass_list: level: 1, count: 8.

gchen_tag: execute_pass_list: level: 1, count: 9.

gchen_tag: execute_pass_list: level: 1, count: 10.

gchen_tag: execute_pass_list: level: 1, count: 11.

gchen_tag: execute_pass_list: level: 1, count: 12.

gchen_tag: execute_pass_list: level: 1, count: 0.

gchen_tag: execute_pass_list: level: 1, count: 1.

gchen_tag: execute_pass_list: level: 1, count: 2.

gchen_tag: execute_pass_list: level: 1, count: 3.

gchen_tag: execute_pass_list: level: 1, count: 4.

gchen_tag: execute_pass_list: level: 1, count: 5.

gchen_tag: execute_pass_list: level: 1, count: 6.

gchen_tag: execute_pass_list: level: 2, count: 0.

gchen_tag: execute_pass_list: level: 2, count: 1.

gchen_tag: execute_pass_list: level: 2, count: 2.

gchen_tag: execute_pass_list: level: 2, count: 3.

gchen_tag: execute_pass_list: level: 2, count: 4.

gchen_tag: execute_pass_list: level: 2, count: 5.

gchen_tag: execute_pass_list: level: 2, count: 6.

gchen_tag: execute_pass_list: level: 2, count: 7.

gchen_tag: execute_pass_list: level: 2, count: 8.

gchen_tag: execute_pass_list: level: 2, count: 9.

gchen_tag: execute_pass_list: level: 2, count: 10.

gchen_tag: execute_pass_list: level: 2, count: 11.

gchen_tag: execute_pass_list: level: 2, count: 12.

gchen_tag: execute_pass_list: level: 2, count: 13.

gchen_tag: execute_pass_list: level: 2, count: 14.

gchen_tag: execute_pass_list: level: 2, count: 15.

gchen_tag: execute_pass_list: level: 2, count: 16.

gchen_tag: execute_pass_list: level: 1, count: 7.

gchen_tag: execute_pass_list: level: 1, count: 8.

gchen_tag: execute_pass_list: level: 1, count: 9.

gchen_tag: execute_pass_list: level: 1, count: 10.

gchen_tag: execute_pass_list: level: 1, count: 0.

gchen_tag: execute_pass_list: level: 2, count: 0.

gchen_tag: execute_pass_list: level: 2, count: 1.

gchen_tag: execute_pass_list: level: 2, count: 2.

gchen_tag: execute_pass_list: level: 2, count: 3.

gchen_tag: execute_pass_list: level: 2, count: 4.

gchen_tag: execute_pass_list: level: 2, count: 5.

gchen_tag: execute_pass_list: level: 2, count: 6.

gchen_tag: execute_pass_list: level: 2, count: 7.

gchen_tag: execute_pass_list: level: 2, count: 8.

gchen_tag: execute_pass_list: level: 2, count: 9.

gchen_tag: execute_pass_list: level: 2, count: 10.

gchen_tag: execute_pass_list: level: 2, count: 11.

gchen_tag: execute_pass_list: level: 2, count: 12.

gchen_tag: execute_pass_list: level: 2, count: 13.

gchen_tag: execute_pass_list: level: 2, count: 14.

gchen_tag: execute_pass_list: level: 2, count: 15.

gchen_tag: execute_pass_list: level: 2, count: 16.

gchen_tag: execute_pass_list: level: 2, count: 17.

gchen_tag: execute_pass_list: level: 2, count: 18.

gchen_tag: execute_pass_list: level: 2, count: 19.

gchen_tag: execute_pass_list: level: 2, count: 20.

gchen_tag: execute_pass_list: level: 2, count: 21.

gchen_tag: execute_pass_list: level: 2, count: 22.

gchen_tag: execute_pass_list: level: 2, count: 23.

gchen_tag: execute_pass_list: level: 2, count: 24.

gchen_tag: execute_pass_list: level: 2, count: 25.

gchen_tag: execute_pass_list: level: 2, count: 26.

gchen_tag: execute_pass_list: level: 2, count: 27.

gchen_tag: execute_pass_list: level: 2, count: 28.

gchen_tag: execute_pass_list: level: 2, count: 29.

gchen_tag: execute_pass_list: level: 2, count: 30.

gchen_tag: execute_pass_list: level: 2, count: 31.

gchen_tag: execute_pass_list: level: 2, count: 32.

gchen_tag: execute_pass_list: level: 2, count: 33.

gchen_tag: execute_pass_list: level: 2, count: 34.

gchen_tag: execute_pass_list: level: 2, count: 35.

gchen_tag: execute_pass_list: level: 2, count: 36.

gchen_tag: execute_pass_list: level: 2, count: 37.

gchen_tag: execute_pass_list: level: 2, count: 38.

gchen_tag: execute_pass_list: level: 2, count: 39.

gchen_tag: execute_pass_list: level: 2, count: 40.

gchen_tag: execute_pass_list: level: 2, count: 41.

gchen_tag: execute_pass_list: level: 2, count: 42.

gchen_tag: execute_pass_list: level: 3, count: 0.

gchen_tag: execute_pass_list: level: 3, count: 1.

gchen_tag: execute_pass_list: level: 3, count: 2.

gchen_tag: execute_pass_list: level: 3, count: 3.

gchen_tag: execute_pass_list: level: 3, count: 4.

gchen_tag: execute_pass_list: level: 3, count: 5.

gchen_tag: execute_pass_list: level: 3, count: 6.

gchen_tag: execute_pass_list: level: 3, count: 7.

gchen_tag: execute_pass_list: level: 3, count: 8.

gchen_tag: execute_pass_list: level: 3, count: 9.

gchen_tag: execute_pass_list: level: 3, count: 10.

gchen_tag: execute_pass_list: level: 3, count: 11.

gchen_tag: execute_pass_list: level: 3, count: 12.

gchen_tag: execute_pass_list: level: 3, count: 13.

gchen_tag: execute_pass_list: level: 3, count: 14.

gchen_tag: execute_pass_list: level: 3, count: 15.

gchen_tag: execute_pass_list: level: 3, count: 16.

gchen_tag: execute_pass_list: level: 3, count: 17.

gchen_tag: execute_pass_list: level: 3, count: 18.

gchen_tag: execute_pass_list: level: 3, count: 19.

gchen_tag: execute_pass_list: level: 3, count: 20.

gchen_tag: execute_pass_list: level: 3, count: 21.

gchen_tag: execute_pass_list: level: 2, count: 43.

gchen_tag: execute_pass_list: level: 2, count: 44.

gchen_tag: execute_pass_list: level: 2, count: 45.

gchen_tag: execute_pass_list: level: 2, count: 46.

gchen_tag: execute_pass_list: level: 2, count: 47.

gchen_tag: execute_pass_list: level: 2, count: 48.

gchen_tag: execute_pass_list: level: 2, count: 49.

gchen_tag: execute_pass_list: level: 2, count: 50.

gchen_tag: execute_pass_list: level: 2, count: 51.

gchen_tag: execute_pass_list: level: 2, count: 52.

gchen_tag: execute_pass_list: level: 2, count: 53.

gchen_tag: execute_pass_list: level: 2, count: 54.

gchen_tag: execute_pass_list: level: 2, count: 55.

gchen_tag: execute_pass_list: level: 2, count: 56.

gchen_tag: execute_pass_list: level: 2, count: 57.

gchen_tag: execute_pass_list: level: 2, count: 58.

gchen_tag: execute_pass_list: level: 2, count: 59.

gchen_tag: execute_pass_list: level: 2, count: 60.

gchen_tag: execute_pass_list: level: 2, count: 61.

gchen_tag: execute_pass_list: level: 2, count: 62.

gchen_tag: execute_pass_list: level: 2, count: 63.

gchen_tag: execute_pass_list: level: 1, count: 1.

gchen_tag: execute_pass_list: level: 1, count: 2.

gchen_tag: execute_pass_list: level: 1, count: 3.

gchen_tag: execute_pass_list: level: 1, count: 4.

gchen_tag: execute_pass_list: level: 1, count: 5.

gchen_tag: execute_pass_list: level: 1, count: 6.

gchen_tag: execute_pass_list: level: 1, count: 7.

gchen_tag: execute_pass_list: level: 1, count: 8.

gchen_tag: execute_pass_list: level: 1, count: 9.

gchen_tag: execute_pass_list: level: 1, count: 10.

gchen_tag: execute_pass_list: level: 1, count: 11.

gchen_tag: execute_pass_list: level: 1, count: 12.

gchen_tag: execute_pass_list: level: 1, count: 13.

gchen_tag: execute_pass_list: level: 1, count: 14.

gchen_tag: execute_pass_list: level: 1, count: 15.

gchen_tag: execute_pass_list: level: 2, count: 0.

gchen_tag: execute_pass_list: level: 2, count: 1.

gchen_tag: execute_pass_list: level: 2, count: 2.

gchen_tag: execute_pass_list: level: 2, count: 3.

gchen_tag: execute_pass_list: level: 2, count: 4.

gchen_tag: execute_pass_list: level: 2, count: 5.

gchen_tag: execute_pass_list: level: 2, count: 6.

gchen_tag: execute_pass_list: level: 2, count: 7.

gchen_tag: execute_pass_list: level: 2, count: 8.

gchen_tag: execute_pass_list: level: 2, count: 9.

gchen_tag: execute_pass_list: level: 2, count: 10.

gchen_tag: execute_pass_list: level: 2, count: 11.

gchen_tag: execute_pass_list: level: 2, count: 12.

gchen_tag: execute_pass_list: level: 2, count: 13.

gchen_tag: execute_pass_list: level: 2, count: 14.

gchen_tag: execute_pass_list: level: 3, count: 0.

gchen_tag: execute_pass_list: level: 3, count: 1.

gchen_tag: execute_pass_list: level: 3, count: 2.

gchen_tag: execute_pass_list: level: 3, count: 3.

gchen_tag: execute_pass_list: level: 3, count: 4.

gchen_tag: execute_pass_list: level: 3, count: 5.

gchen_tag: execute_pass_list: level: 2, count: 15.

gchen_tag: execute_pass_list: level: 2, count: 16.

gchen_tag: execute_pass_list: level: 2, count: 17.

gchen_tag: execute_pass_list: level: 2, count: 18.

gchen_tag: execute_pass_list: level: 2, count: 19.

gchen_tag: execute_pass_list: level: 2, count: 20.

gchen_tag: execute_pass_list: level: 2, count: 21.

gchen_tag: execute_pass_list: level: 2, count: 22.

gchen_tag: execute_pass_list: level: 2, count: 23.

gchen_tag: execute_pass_list: level: 2, count: 24.

gchen_tag: execute_pass_list: level: 2, count: 25.

gchen_tag: execute_pass_list: level: 2, count: 26.

gchen_tag: execute_pass_list: level: 2, count: 27.

gchen_tag: execute_pass_list: level: 2, count: 28.

gchen_tag: execute_pass_list: level: 2, count: 29.

gchen_tag: execute_pass_list: level: 2, count: 30.

gchen_tag: execute_pass_list: level: 2, count: 31.

gchen_tag: execute_pass_list: level: 2, count: 32.

gchen_tag: execute_pass_list: level: 2, count: 33.

gchen_tag: execute_pass_list: level: 2, count: 34.

gchen_tag: execute_pass_list: level: 2, count: 35.

gchen_tag: execute_pass_list: level: 2, count: 36.

gchen_tag: execute_pass_list: level: 2, count: 37.

gchen_tag: execute_pass_list: level: 2, count: 38.

gchen_tag: execute_pass_list: level: 3, count: 0.

gchen_tag: execute_pass_list: level: 3, count: 1.

gchen_tag: execute_pass_list: level: 3, count: 2.

gchen_tag: execute_pass_list: level: 3, count: 3.

gchen_tag: execute_pass_list: level: 3, count: 4.

gchen_tag: execute_pass_list: level: 3, count: 5.

gchen_tag: execute_pass_list: level: 3, count: 6.

gchen_tag: execute_pass_list: level: 3, count: 7.

gchen_tag: execute_pass_list: level: 3, count: 8.

gchen_tag: execute_pass_list: level: 3, count: 9.

gchen_tag: execute_pass_list: level: 3, count: 10.

gchen_tag: execute_pass_list: level: 3, count: 11.

gchen_tag: execute_pass_list: level: 3, count: 12.

gchen_tag: execute_pass_list: level: 3, count: 13.

gchen_tag: execute_pass_list: level: 3, count: 14.

gchen_tag: execute_pass_list: level: 3, count: 15.

gchen_tag: execute_pass_list: level: 3, count: 16.

gchen_tag: execute_pass_list: level: 3, count: 17.

gchen_tag: execute_pass_list: level: 3, count: 18.

gchen_tag: execute_pass_list: level: 3, count: 19.

gchen_tag: execute_pass_list: level: 3, count: 20.

gchen_tag: execute_pass_list: level: 3, count: 21.

gchen_tag: execute_pass_list: level: 3, count: 22.

gchen_tag: execute_pass_list: level: 3, count: 23.

gchen_tag: execute_pass_list: level: 3, count: 24.

gchen_tag: execute_pass_list: level: 3, count: 25.

gchen_tag: execute_pass_list: level: 3, count: 26.

gchen_tag: execute_pass_list: level: 3, count: 27.

gchen_tag: execute_pass_list: level: 3, count: 28.

gchen_tag: execute_pass_list: level: 3, count: 29.

gchen_tag: execute_pass_list: level: 3, count: 30.

gchen_tag: execute_pass_list: level: 3, count: 31.

gchen_tag: can brreak in execute_pass_list.

gchen_tag: call maybe_record_trace_start: idx = 7

gchen_tag: scan_trace in create_cfi_notes count = 0

gchen_tag: scan_trace in create_cfi_notes count = 1

gchen_tag: call maybe_record_trace_start: idx = 3

gchen_tag: scan_trace in create_cfi_notes count = 2

gchen_tag: scan_trace in create_cfi_notes count = 3

gchen_tag: scan_trace in create_cfi_notes count = 4

gchen_tag: call maybe_record_trace_start: idx = 2

gchen_tag: scan_trace in create_cfi_notes count = 5

gchen_tag: scan_trace break.

gchen_tag: call maybe_record_trace_start: idx = 6

gchen_tag: scan_trace in create_cfi_notes count = 6

gchen_tag: call maybe_record_trace_start: idx = 18

gchen_tag: call maybe_record_trace_start need break.
/tmp/ana/namei/namei.c: In function 'SYSC_mknodat':
/tmp/ana/namei/namei.c:40:1: internal compiler error: in
maybe_record_trace_start, at dwarf2cfi.c:2218
 }
 ^
0x6da1a4 maybe_record_trace_start
    ../../gcc-4.9.0/gcc/dwarf2cfi.c:2218
0x6da82a scan_trace
    ../../gcc-4.9.0/gcc/dwarf2cfi.c:2399
0x6dadea create_cfi_notes
    ../../gcc-4.9.0/gcc/dwarf2cfi.c:2557
0x6db8e4 execute_dwarf2_frame
    ../../gcc-4.9.0/gcc/dwarf2cfi.c:2912
0x6dc5e2 execute
    ../../gcc-4.9.0/gcc/dwarf2cfi.c:3408
Please submit a full bug report,


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Bug c/58256] gcc for h8300  internal compiler error: in maybe_record_trace_start
  2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
                   ` (7 preceding siblings ...)
  2013-09-15 12:27 ` gang.chen at asianux dot com
@ 2013-09-16  4:37 ` gang.chen at asianux dot com
  2013-09-16  8:20 ` gang.chen at asianux dot com
                   ` (3 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: gang.chen at asianux dot com @ 2013-09-16  4:37 UTC (permalink / raw)
  To: gcc-bugs

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=30825&action=edit
Issue is within xgcc, can exclude cc1 by comparing the summary log between
gcc-4.8.0 and gcc-4.9.0.

By comparing the summary log between gcc-4.8.0 and gcc-4.9.0, the issue is
within xgcc, we can exclude cc1.

The attachment contents 3 files.

  err.diff: the gcc-4.9.0 summary log.
  correct.diff: the gcc-4.8.0 summary log.
  info.diff: my modification for gcc-4.9.0, so can print the related summary
log
               (the same modification for gcc-4.8.0)

I will continue to analyzing the details within xgcc, and also print more
related varaibles for analyzing.


Welcome any additional suggestions and completions, thanks.


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Bug c/58256] gcc for h8300  internal compiler error: in maybe_record_trace_start
  2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
                   ` (8 preceding siblings ...)
  2013-09-16  4:37 ` gang.chen at asianux dot com
@ 2013-09-16  8:20 ` gang.chen at asianux dot com
  2013-09-16 11:27 ` gang.chen at asianux dot com
                   ` (2 subsequent siblings)
  12 siblings, 0 replies; 14+ messages in thread
From: gang.chen at asianux dot com @ 2013-09-16  8:20 UTC (permalink / raw)
  To: gcc-bugs

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=30826&action=edit
(sorry, it is cc1 issue) It is the related command line for cc1 and the summary
work flow for gcc-4.8.0 and gcc-4.9.0

Oh, sorry, the comments #9 is obsoleted, it is not caused by xgcc (although
their work flow are different with each other), our issue is cc1 issue.

The attachment is the related command line for cc1 and the summary call flow
for gcc-4.8.0 and gcc-4.9.0.

I will continue to analyze the first different between them.

Welcome any suggestions and completions, thanks.


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Bug c/58256] gcc for h8300  internal compiler error: in maybe_record_trace_start
  2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
                   ` (9 preceding siblings ...)
  2013-09-16  8:20 ` gang.chen at asianux dot com
@ 2013-09-16 11:27 ` gang.chen at asianux dot com
  2015-01-11 13:00 ` [Bug target/58256] " gang.chen.5i5j at gmail dot com
  2015-01-11 13:02 ` gang.chen.5i5j at gmail dot com
  12 siblings, 0 replies; 14+ messages in thread
From: gang.chen at asianux dot com @ 2013-09-16 11:27 UTC (permalink / raw)
  To: gcc-bugs

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 (although I still don't know how to use it now).

3. that means: what I have done above is almost all 'spam'.  :-(


I will continue trying tomorrow.


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Bug target/58256] gcc for h8300  internal compiler error: in maybe_record_trace_start
  2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
                   ` (10 preceding siblings ...)
  2013-09-16 11:27 ` gang.chen at asianux dot com
@ 2015-01-11 13:00 ` gang.chen.5i5j at gmail dot com
  2015-01-11 13:02 ` gang.chen.5i5j at gmail dot com
  12 siblings, 0 replies; 14+ messages in thread
From: gang.chen.5i5j at gmail dot com @ 2015-01-11 13:00 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58256

--- Comment #13 from Chen Gang <gang.chen.5i5j at gmail dot com> ---
For gcc version 5.0.0 20150109 (experimental) (GCC), can not find this issue
again. So at present, we can close it.


^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Bug target/58256] gcc for h8300  internal compiler error: in maybe_record_trace_start
  2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
                   ` (11 preceding siblings ...)
  2015-01-11 13:00 ` [Bug target/58256] " gang.chen.5i5j at gmail dot com
@ 2015-01-11 13:02 ` gang.chen.5i5j at gmail dot com
  12 siblings, 0 replies; 14+ messages in thread
From: gang.chen.5i5j at gmail dot com @ 2015-01-11 13:02 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58256

Chen Gang <gang.chen.5i5j at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #14 from Chen Gang <gang.chen.5i5j at gmail dot com> ---
For gcc version 5.0.0 20150109 (experimental) (GCC), can not find this issue
again. So at present, we can mark it as FIXED


^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~2015-01-11 13:02 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-28  3:22 [Bug c/58256] New: gcc for h8300 internal compiler error: in maybe_record_trace_start gang.chen at asianux dot com
2013-09-12  3:34 ` [Bug c/58256] " gang.chen at asianux dot com
2013-09-12  3:36 ` gang.chen at asianux dot com
2013-09-12  3:44 ` gang.chen at asianux dot com
2013-09-12  3:45 ` gang.chen at asianux dot com
2013-09-13  3:14 ` gang.chen at asianux dot com
2013-09-13 21:20 ` law at redhat dot com
2013-09-14 16:47 ` gang.chen at asianux dot com
2013-09-15 12:27 ` gang.chen at asianux dot com
2013-09-16  4:37 ` gang.chen at asianux dot com
2013-09-16  8:20 ` gang.chen at asianux dot com
2013-09-16 11:27 ` gang.chen at asianux dot com
2015-01-11 13:00 ` [Bug target/58256] " gang.chen.5i5j at gmail dot com
2015-01-11 13:02 ` gang.chen.5i5j at gmail dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).