From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8115 invoked by alias); 3 Oct 2006 16:48:29 -0000 Received: (qmail 8015 invoked by uid 48); 3 Oct 2006 16:48:18 -0000 Date: Tue, 03 Oct 2006 16:48:00 -0000 Subject: [Bug middle-end/29335] New: transcendental functions with constant arguments should be resolved at compile-time X-Bugzilla-Reason: CC Message-ID: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "ghazi at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-10/txt/msg00247.txt.bz2 List-Id: 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