From: "G. Sumner Hayes" <zumner@collegium.adsl.net.cmu.edu>
To: egcs@cygnus.com
Subject: -fprofile-arcs and -fbranch-probabilities
Date: Fri, 05 Dec 1997 18:45:00 -0000 [thread overview]
Message-ID: <19971205214936.11384@collegium.adsl.net.cmu.edu> (raw)
Are -fprofile-arcs and -fbranch-probabilities supposed to be stable
in egcs-1.0, or are they still under development?
Compiling with -fprofile-arcs works fine and running the resulting
executable generates many .da files; trying to compile the results
with -fbranch-probabilities gives mixed results. Some files compile
fine. Some have warnings (shown below). Some cause cc1 to get fatal
signal 6 and die (shown below). If this is expected, fine; if not,
any ideas what's causing it?
Warnings are often of this form:
../bbox.c: In function `Destroy_Bounding_Slabs':
../bbox.c:1909: warning: Arc profiling: some arc counts were bad.
../bbox.c: In function `Destroy_BBox_Tree':
../bbox.c:1909: warning: Arc profiling: some arc counts were bad.
../bbox.c: In function `Create_Rayinfo':
../bbox.c:1909: warning: Arc profiling: some arc counts were bad.
../bbox.c: In function `create_bbox_node':
../bbox.c:1909: warning: Arc profiling: some arc counts were bad.
../bbox.c: In function `calc_bbox':
../bbox.c:1909: warning: Arc profiling: some arc counts were bad.
../bbox.c: At top level:
../bbox.c:1909: warning: .da file contents not exhausted
Some files die with errors like the following:
../boxes.c: In function `Intersect_Box':
../boxes.c:528: internal error--unrecognizable insn:
(jump_insn/s 92 91 94 (set (pc)
(if_then_else (le (cc0)
(const_int 10000))
(label_ref 157)
(pc))) -1 (insn_list:REG_DEP_ANTI 82 (insn_list:REG_DEP_ANTI 84 (insn_list 89 (insn_list 88 (nil)))))
(expr_list:REG_BR_PROB (const_int 5809)
(nil)))
gcc: Internal compiler error: program cc1 got fatal signal 6
Thanks for your time,
Sumner
--
rage, rage against the dying of the light
reply other threads:[~1997-12-05 18:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19971205214936.11384@collegium.adsl.net.cmu.edu \
--to=zumner@collegium.adsl.net.cmu.edu \
--cc=egcs@cygnus.com \
/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).