public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/29049] possible problem: building gcc >= 4.2 on i686 GNU/Linux|SMP (non-64bit) platform fails
Date: Wed, 13 Sep 2006 15:03:00 -0000	[thread overview]
Message-ID: <20060913150324.1355.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29049-13226@http.gcc.gnu.org/bugzilla/>



------- Comment #28 from hjl at lucon dot org  2006-09-13 15:03 -------
Apparently, your target_flags sets MASK_64BIT. You need to run gdb on cc1 and
set hardware watchpoint on target_flags to see where it sets MASK_64BIT:

[hjl@gnu-3 gcc]$ touch x.i
[hjl@gnu-3 gcc]$ gdb cc1
GNU gdb 6.4.50.20060406-cvs
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db
library "/lib/tls/libthread_db.so.1".

Breakpoint 1 at 0x8138b96: file ../../gcc/diagnostic.c, line 602.
Breakpoint 2 at 0x8138b43: file ../../gcc/diagnostic.c, line 547.
Function "exit" not defined.
Function "abort" not defined.
(gdb) watch target_flags
Hardware watchpoint 3: target_flags
(gdb) r -fpreprocessed x.i -quiet -dumpbase x.i -mtune=pentiumpro -auxbase x
-version -o x.s
Starting program: /export/gnu/import/gcc-4.1.0/build/gcc/cc1 -fpreprocessed x.i
-quiet -dumpbase x.i -mtune=pentiumpro -auxbase x -version -o x.s
Hardware watchpoint 3: target_flags
Hardware watchpoint 3: target_flags
Hardware watchpoint 3: target_flags

Old value = 0
New value = 8388808
decode_options (argc=12, argv=0xbff24ef4) at ../../gcc/opts.c:634
634       flag_unwind_tables = targetm.unwind_tables_default;
(gdb) c
Continuing.
During symbol reading, incomplete CFI data; unspecified registers (e.g., eax)
at 0x828dfc3.
During symbol reading, incomplete CFI data; unspecified registers (e.g., ecx)
at 0x828dfc3.
During symbol reading, incomplete CFI data; unspecified registers (e.g., edx)
at 0x828dfc3.
During symbol reading, incomplete CFI data; unspecified registers (e.g., eax)
at 0x830f53c.
During symbol reading, incomplete CFI data; unspecified registers (e.g., ecx)
at 0x830f53c.
During symbol reading, incomplete CFI data; unspecified registers (e.g., edx)
at 0x830f53c.
Hardware watchpoint 3: target_flags

Old value = 8388808
New value = 8405192
override_options () at ../../gcc/config/i386/i386.c:1614
1614      if (TARGET_SSEREGPARM
(gdb) c
Continuing.
During symbol reading, incomplete CFI data; unspecified registers (e.g., eax)
at 0x830f53c.
During symbol reading, incomplete CFI data; unspecified registers (e.g., ecx)
at 0x830f53c.
During symbol reading, incomplete CFI data; unspecified registers (e.g., edx)
at 0x830f53c.
Hardware watchpoint 3: target_flags

Old value = 8405192
New value = 8405208
override_options () at ../../gcc/config/i386/i386.c:1667
1667      if ((flag_unwind_tables || flag_asynchronous_unwind_tables
(gdb) c
Continuing.
During symbol reading, incomplete CFI data; unspecified registers (e.g., eax)
at 0x830f53c.
During symbol reading, incomplete CFI data; unspecified registers (e.g., ecx)
at 0x830f53c.
During symbol reading, incomplete CFI data; unspecified registers (e.g., edx)
at 0x830f53c.
GNU C version 4.1.0 (i686-pc-linux-gnu)
        compiled by GNU C version 3.4.6 20060404 (Red Hat 3.4.6-3).
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: 2547d670e9349240a4187f725ff2e074

Program exited normally.
(gdb)


-- 


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


  parent reply	other threads:[~2006-09-13 15:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 23:48 [Bug other/29049] New: " WISD00M at GMX dot NET
2006-09-12 23:53 ` [Bug other/29049] " WISD00M at GMX dot NET
2006-09-12 23:53 ` pinskia at gcc dot gnu dot org
2006-09-12 23:54 ` WISD00M at GMX dot NET
2006-09-12 23:54 ` WISD00M at GMX dot NET
2006-09-12 23:55 ` WISD00M at GMX dot NET
2006-09-12 23:56 ` WISD00M at GMX dot NET
2006-09-12 23:57 ` WISD00M at GMX dot NET
2006-09-12 23:58 ` WISD00M at GMX dot NET
2006-09-13  0:10 ` WISD00M at GMX dot NET
2006-09-13  0:12 ` WISD00M at GMX dot NET
2006-09-13  0:14 ` WISD00M at GMX dot NET
2006-09-13  0:24 ` WISD00M at GMX dot NET
2006-09-13  0:27 ` pinskia at gcc dot gnu dot org
2006-09-13  0:30 ` WISD00M at GMX dot NET
2006-09-13  0:36 ` WISD00M at GMX dot NET
2006-09-13  0:44 ` WISD00M at GMX dot NET
2006-09-13  0:51 ` WISD00M at GMX dot NET
2006-09-13  0:57 ` joseph at codesourcery dot com
2006-09-13  1:11 ` WISD00M at GMX dot NET
2006-09-13  1:11 ` WISD00M at GMX dot NET
2006-09-13  1:16 ` WISD00M at GMX dot NET
2006-09-13  2:56 ` hjl at lucon dot org
2006-09-13  3:16 ` WISD00M at GMX dot NET
2006-09-13  3:24 ` WISD00M at GMX dot NET
2006-09-13  5:02 ` WISD00M at GMX dot NET
2006-09-13  5:46 ` hjl at lucon dot org
2006-09-13  6:20 ` WISD00M at GMX dot NET
2006-09-13 15:03 ` hjl at lucon dot org [this message]
2006-10-24  8:19 ` pinskia at gcc dot gnu dot org
2007-08-02  1:14 ` lauras at gcc dot gnu dot org
2007-08-02  1:14 ` lauras at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060913150324.1355.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).