public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug other/29405] New: GCC should include latest GMP/MPFR sources and always build libgmp.a/libmpfr.a
@ 2006-10-09 17:14 ghazi at gcc dot gnu dot org
2006-10-09 17:18 ` [Bug other/29405] " ghazi at gcc dot gnu dot org
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: ghazi at gcc dot gnu dot org @ 2006-10-09 17:14 UTC (permalink / raw)
To: gcc-bugs
I'm using this to track issues related to including GMP/MPFR in the GCC source
tree and building these libraries as part of the bootstrap process.
Initial discussion started here:
http://gcc.gnu.org/ml/gcc/2006-10/msg00136.html
--
Summary: GCC should include latest GMP/MPFR sources and always
build libgmp.a/libmpfr.a
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: other
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=29405
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug other/29405] GCC should include latest GMP/MPFR sources and always build libgmp.a/libmpfr.a
2006-10-09 17:14 [Bug other/29405] New: GCC should include latest GMP/MPFR sources and always build libgmp.a/libmpfr.a ghazi at gcc dot gnu dot org
@ 2006-10-09 17:18 ` ghazi at gcc dot gnu dot org
2006-10-10 8:13 ` fxcoudert at gcc dot gnu dot org
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: ghazi at gcc dot gnu dot org @ 2006-10-09 17:18 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from ghazi at gcc dot gnu dot org 2006-10-09 17:18 -------
Initial patch posted here:
http://gcc.gnu.org/ml/gcc-patches/2006-10/msg00416.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29405
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug other/29405] GCC should include latest GMP/MPFR sources and always build libgmp.a/libmpfr.a
2006-10-09 17:14 [Bug other/29405] New: GCC should include latest GMP/MPFR sources and always build libgmp.a/libmpfr.a ghazi at gcc dot gnu dot org
2006-10-09 17:18 ` [Bug other/29405] " ghazi at gcc dot gnu dot org
@ 2006-10-10 8:13 ` fxcoudert at gcc dot gnu dot org
2006-10-10 13:53 ` vincent at vinc17 dot org
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2006-10-10 8:13 UTC (permalink / raw)
To: gcc-bugs
------- Comment #2 from fxcoudert at gcc dot gnu dot org 2006-10-10 08:13 -------
I'm very interested in that. I think it would really benefit the compiler: the
Fortran front-end would gain much in stability (and ease of installation) and
the C front-end could also benefit from this (as mentionned in PR29335).
What's worrying me a bit is the versioning of MPFR. I'm writing it here because
Vincent is in the Cc list of this bug, so maybe he can answer. The last MPFR
release is dated 2005-09-09, and since then only patches without version
information have been posted. That means we have no way to identify the MPFR
library used exactly, to work around potential bugs or require fine-grained
minimal version. Vincent, would it be possible that some version number is
increased every time a patch is posted, so that the current version would be
2.2.16 or something like that?
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fxcoudert at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29405
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug other/29405] GCC should include latest GMP/MPFR sources and always build libgmp.a/libmpfr.a
2006-10-09 17:14 [Bug other/29405] New: GCC should include latest GMP/MPFR sources and always build libgmp.a/libmpfr.a ghazi at gcc dot gnu dot org
2006-10-09 17:18 ` [Bug other/29405] " ghazi at gcc dot gnu dot org
2006-10-10 8:13 ` fxcoudert at gcc dot gnu dot org
@ 2006-10-10 13:53 ` vincent at vinc17 dot org
2006-10-14 16:09 ` ghazi at gcc dot gnu dot org
2006-10-14 16:10 ` ghazi at gcc dot gnu dot org
4 siblings, 0 replies; 6+ messages in thread
From: vincent at vinc17 dot org @ 2006-10-10 13:53 UTC (permalink / raw)
To: gcc-bugs
------- Comment #3 from vincent at vinc17 dot org 2006-10-10 13:53 -------
(In reply to comment #2)
> What's worrying me a bit is the versioning of MPFR.
Note that GMP is similar.
> Vincent, would it be possible that some version number is increased every
> time a patch is posted, so that the current version would be 2.2.16 or
> something like that?
There has been a very short discussion about that last year:
http://sympa.loria.fr/wwsympa/arc/mpfr/2005-12/msg00049.html
The problem is that it is not that simple. First, for some reasons, not all
patches committed to the 2.2 branch are put on the 2.2.0 web page, so that the
future 2.2.1 version will not just be 2.2.0 + the patches provided on the web
page. We could provide another way to identify the patches, but as said in the
cited URL, this could be done only as of MPFR 2.3.0 (possibly except if one
decides just to add a macro to mpfr.h for this purpose). The main problem is
that one may want to apply some patches, but not others, or identify builds
from the Subversion repository... For instance, the macro could contain a group
of tags (e.g. the name of the patches and possibly some other information). But
how would this macro be used by gcc and other software? Would a group of tags
be useful, or too complex?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29405
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug other/29405] GCC should include latest GMP/MPFR sources and always build libgmp.a/libmpfr.a
2006-10-09 17:14 [Bug other/29405] New: GCC should include latest GMP/MPFR sources and always build libgmp.a/libmpfr.a ghazi at gcc dot gnu dot org
` (2 preceding siblings ...)
2006-10-10 13:53 ` vincent at vinc17 dot org
@ 2006-10-14 16:09 ` ghazi at gcc dot gnu dot org
2006-10-14 16:10 ` ghazi at gcc dot gnu dot org
4 siblings, 0 replies; 6+ messages in thread
From: ghazi at gcc dot gnu dot org @ 2006-10-14 16:09 UTC (permalink / raw)
To: gcc-bugs
------- Comment #4 from ghazi at gcc dot gnu dot org 2006-10-14 16:09 -------
I think we're converging on not including these libraries in the GCC tree, but
rather to require the user to be responsible for getting them.
http://gcc.gnu.org/ml/gcc/2006-10/msg00167.html
Either way, GCC can always rely on MPFR being available, and I can start using
it in the middle-end.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29405
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug other/29405] GCC should include latest GMP/MPFR sources and always build libgmp.a/libmpfr.a
2006-10-09 17:14 [Bug other/29405] New: GCC should include latest GMP/MPFR sources and always build libgmp.a/libmpfr.a ghazi at gcc dot gnu dot org
` (3 preceding siblings ...)
2006-10-14 16:09 ` ghazi at gcc dot gnu dot org
@ 2006-10-14 16:10 ` ghazi at gcc dot gnu dot org
4 siblings, 0 replies; 6+ messages in thread
From: ghazi at gcc dot gnu dot org @ 2006-10-14 16:10 UTC (permalink / raw)
To: gcc-bugs
------- Comment #5 from ghazi at gcc dot gnu dot org 2006-10-14 16:10 -------
Won't fix.
--
ghazi at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WONTFIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29405
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-10-14 16:10 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-10-09 17:14 [Bug other/29405] New: GCC should include latest GMP/MPFR sources and always build libgmp.a/libmpfr.a ghazi at gcc dot gnu dot org
2006-10-09 17:18 ` [Bug other/29405] " ghazi at gcc dot gnu dot org
2006-10-10 8:13 ` fxcoudert at gcc dot gnu dot org
2006-10-10 13:53 ` vincent at vinc17 dot org
2006-10-14 16:09 ` ghazi at gcc dot gnu dot org
2006-10-14 16:10 ` ghazi at gcc dot gnu dot org
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).