public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/29335] New: transcendental functions with constant arguments should be resolved at compile-time Date: Tue, 03 Oct 2006 16:48:00 -0000 [thread overview] Message-ID: <bug-29335-578@http.gcc.gnu.org/bugzilla/> (raw) We should use GMP/MPFR from inside builtins.c to resolve things like e.g. cos(0.12345) at compile-time. Need to figure out: 1. Whether a certain minimum version of GMP/MPFR is required to avoid known bugs, etc. 2. Whether we should include GMP/MPFR in the svn archive like we do for intl and zlib. 3. Whether GMP/MPFR works on all the platforms/configurations that GCC supports. Are we ready to require a GMP/MPFR port for every port of GCC? 4. If we don't do #2 and there is no system GMP/MPFR or the system lib is too old, or if we trip over #3 and can't have GMP/MPFR, then what? Do we require the user to go get/port it, or silently eliminate this optimization during the build process? -- Summary: transcendental functions with constant arguments should be resolved at compile-time Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ghazi at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29335
next reply other threads:[~2006-10-03 16:48 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-03 16:48 ghazi at gcc dot gnu dot org [this message] 2006-10-05 5:11 ` [Bug middle-end/29335] " pinskia at gcc dot gnu dot org 2006-10-05 17:54 ` kargl at gcc dot gnu dot org 2006-10-06 13:25 ` ghazi at gcc dot gnu dot org 2006-10-06 14:40 ` kargl at gcc dot gnu dot org 2006-10-06 15:36 ` ghazi at gcc dot gnu dot org 2006-10-06 17:03 ` kargl at gcc dot gnu dot org 2006-10-07 2:05 ` ghazi at gcc dot gnu dot org 2006-10-07 14:08 ` ghazi at gcc dot gnu dot org 2006-10-09 17:16 ` ghazi at gcc dot gnu dot org 2006-10-14 16:12 ` ghazi at gcc dot gnu dot org 2006-10-14 16:14 ` ghazi at gcc dot gnu dot org 2006-10-20 15:54 ` ghazi at gcc dot gnu dot org 2006-10-23 20:25 ` ghazi at gcc dot gnu dot org 2006-10-24 17:45 ` ghazi at gcc dot gnu dot org 2006-10-25 20:44 ` ghazi at gcc dot gnu dot org 2006-10-28 3:20 ` ghazi at gcc dot gnu dot org 2006-10-28 3:48 ` sgk at troutmask dot apl dot washington dot edu 2006-10-28 9:07 ` vincent at vinc17 dot org 2006-10-28 13:29 ` ghazi at gcc dot gnu dot org 2006-10-28 14:06 ` vincent at vinc17 dot org 2006-10-28 16:04 ` ghazi at gcc dot gnu dot org 2006-10-28 16:58 ` vincent at vinc17 dot org 2006-10-29 2:02 ` ghazi at gcc dot gnu dot org 2006-10-30 20:22 ` ghazi at gcc dot gnu dot org 2006-10-31 3:14 ` ghazi at gcc dot gnu dot org 2006-10-31 9:55 ` vincent at vinc17 dot org 2006-10-31 20:09 ` ghazi at gcc dot gnu dot org 2006-10-31 22:15 ` vincent at vinc17 dot org 2006-11-02 3:21 ` ghazi at gcc dot gnu dot org 2006-11-02 14:41 ` ghazi at gcc dot gnu dot org 2006-11-02 15:57 ` vincent at vinc17 dot org 2006-11-02 22:44 ` ghazi at gcc dot gnu dot org 2006-11-05 23:27 ` vincent at vinc17 dot org 2006-11-07 2:46 ` ghazi at gcc dot gnu dot org 2006-11-30 19:45 ` chaoyingfu at gcc dot gnu dot org 2006-12-18 14:54 ` ghazi at gcc dot gnu dot org 2006-12-26 19:03 ` ghazi at gcc dot gnu dot org 2006-12-26 19:13 ` ghazi at gcc dot gnu dot org 2007-01-20 0:33 ` ghazi at gcc dot gnu dot org 2007-01-31 15:06 ` ghazi 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=bug-29335-578@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).