https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
Sam James changed:
What|Removed |Added
Resolution|WONTFIX |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
mmokrejs at gmail dot com changed:
What|Removed |Added
CC||mmokrejs at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #28 from Richard Guenther rguenth at gcc dot gnu.org 2012-08-06
08:42:57 UTC ---
(In reply to comment #26)
Well, when I read on the documentation page
http://gcc.gnu.org/install/configure.html
--enable-build-with-cxx
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #29 from Steven Bosscher steven at gcc dot gnu.org 2012-08-06
09:10:49 UTC ---
(In reply to comment #27)
Actually, I'm more interested in seeing if insn-emit.c can be reduced in size
by avoiding duplicate functions (see e.g.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #30 from Steven Bosscher steven at gcc dot gnu.org 2012-08-06
10:49:03 UTC ---
Created attachment 27950
-- http://gcc.gnu.org/bugzilla/attachment.cgi?id=27950
Split insn-emit.c into four separate files
Untested, etc., and doesn't
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #1 from Jason Vas Dias jason.vas.dias at gmail dot com 2012-08-05
11:11:28 UTC ---
Why must we compile 1.8MB of insn-emit.c ?
Can't it be split up ?
Why is gcc-4.7.1 SO much slower ?
ie. evidently the Stage1 and Stage2 compilers
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
wbrana wbrana at gmail dot com changed:
What|Removed |Added
CC||wbrana at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #3 from Jason Vas Dias jason.vas.dias at gmail dot com 2012-08-05
11:36:05 UTC ---
RE:
Your PC is broken.
Comments such as these don't help much.
No, only Linux 3.4+ temperature management is.
I'm working with the Linux developers to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #4 from Jason Vas Dias jason.vas.dias at gmail dot com 2012-08-05
11:43:03 UTC ---
in case the configuration is relevant:
quote file=config.log
It was created by configure, which was
generated by GNU Autoconf 2.64. Invocation
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #5 from wbrana wbrana at gmail dot com 2012-08-05 12:00:50 UTC ---
(In reply to comment #3)
And what type of super-computer is that ?
outdated, almost 5 years old: Core 2 Quad 3.2 GHz, 4 GB RAM
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
Steven Bosscher steven at gcc dot gnu.org changed:
What|Removed |Added
CC||steven at gcc
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #7 from Jason Vas Dias jason.vas.dias at gmail dot com 2012-08-05
12:21:10 UTC ---
Thanks for your response !
I think the cc1 process is somehow operating in slow motion,
even though I've pinned the CPU frequency to 1.8 GHz (it
will
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #8 from wbrana wbrana at gmail dot com 2012-08-05 12:27:52 UTC ---
2 GB RAM isn't enough.
It isn't good idea to use x86_64 with 2 GB RAM.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #9 from Steven Bosscher steven at gcc dot gnu.org 2012-08-05
12:33:56 UTC ---
(In reply to comment #7)
cc1 is writing about one line every 2 minutes to its assembler output file:
If you've really configured with
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #10 from Steven Bosscher steven at gcc dot gnu.org 2012-08-05
12:37:28 UTC ---
(In reply to comment #7)
These memory requirements are solely due to the size of the .c file (1.8MB) .
This is indeed excessive, we'll have to look into
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #11 from Jason Vas Dias jason.vas.dias at gmail dot com
2012-08-05 13:16:03 UTC ---
Thanks for the responses - I will try again with
'--enable-checking=release'.
But, I still don't think this bug is a non-issue - here's why:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #12 from wbrana wbrana at gmail dot com 2012-08-05 13:31:28 UTC
---
embedded systems compiler doesn't mean you can run gcc on embedded system, but
you can cross compile for embedded system.
Average user doesn't build or use compiler.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #13 from Jason Vas Dias jason.vas.dias at gmail dot com
2012-08-05 13:43:21 UTC ---
RE: Steven Bosscher 2012-08-05 12:37:28 UTC \
(In reply to comment #7)
These memory requirements are solely due to the size of the .c file (1.8MB) .
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #14 from Jason Vas Dias jason.vas.dias at gmail dot com
2012-08-05 13:46:26 UTC ---
$ time /mnt/sda3/gcc/./prev-gcc/xgcc -B/mnt/sda3/gcc/./prev-gcc/
-B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/bin/
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #15 from Jason Vas Dias jason.vas.dias at gmail dot com
2012-08-05 13:51:27 UTC ---
Created attachment 27939
-- http://gcc.gnu.org/bugzilla/attachment.cgi?id=27939
pre-processed C from previous comment command
$ xz --uncompress
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #16 from Steven Bosscher steven at gcc dot gnu.org 2012-08-05
13:54:30 UTC ---
$ /usr/build2/gcc/gcc-4.7.1/configure --prefix=/usr --libdir=/usr/lib64 \
--enable-multilib --with-cpu-32=i686 --with-cpu-64=k8 \
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #17 from Steven Bosscher steven at gcc dot gnu.org 2012-08-05
13:55:43 UTC ---
(In reply to comment #12)
Average user doesn't build or use compiler. It is only done by developers
which
have modern PC which means 8 GB RAM.
Sorry,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #18 from wbrana wbrana at gmail dot com 2012-08-05 14:11:37 UTC
---
(In reply to comment #17)
Sorry, but this is just rubbish.
You didn't confute my statements.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #20 from Jason Vas Dias jason.vas.dias at gmail dot com
2012-08-05 18:10:24 UTC ---
RE: --disable-bootstrap if you're doing --enable-gather-statistics
but for me this defeats the whole purpose of building a C-only
bootstrap
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
Steven Bosscher steven at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #22 from Jason Vas Dias jason.vas.dias at gmail dot com
2012-08-05 19:48:45 UTC ---
RE:
If you want a C-only compiler then you should just configure with
--enable-languages=c only
of course, I tried that first, but that is no
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #23 from Jason Vas Dias jason.vas.dias at gmail dot com
2012-08-05 19:51:56 UTC ---
Yes, I was wondering how long it would take to close this bug as INVALID,
which seems to be the standard response to uncomfortable bug reports these
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #24 from Jason Vas Dias jason.vas.dias at gmail dot com
2012-08-05 20:10:36 UTC ---
$ ps -lp 3863
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
0 R 0 3863 3862 99 80 0 - 64611 - pts/5
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
Steven Bosscher steven at gcc dot gnu.org changed:
What|Removed |Added
Resolution|INVALID |WONTFIX
---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #26 from Jason Vas Dias jason.vas.dias at gmail dot com
2012-08-05 20:57:59 UTC ---
Well, when I read on the documentation page
http://gcc.gnu.org/install/configure.html
--enable-build-with-cxx
Build GCC using a C++ compiler
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #27 from Steven Bosscher steven at gcc dot gnu.org 2012-08-05
21:05:41 UTC ---
(In reply to comment #26)
And what has any of this to do with the simple question posed in the title
of this bug report : why can't insn-emit.c be split
31 matches
Mail list logo
