Re: bootstrap broken on PPC-darwin and other targets without pkg-config (which is almost all)
Andrew Pinski wrote:
Caused by:
http://gcc.gnu.org/ml/gcc-cvs/2006-06/msg00225.html
I committed this fix.
Tom
2006-06-10 Thomas Fitzsimmons <[EMAIL PROTECTED]>
* configure.ac (ac_configure_args): Add --disable-plugin.
(--enable-gtk-cairo): Remove option.
* configure: Regenerate.
Index: configure.ac
===
--- configure.ac (revision 114539)
+++ configure.ac (working copy)
@@ -330,6 +330,7 @@
dnl FIXME?
ac_configure_args="$ac_configure_args --disable-examples"
ac_configure_args="$ac_configure_args --with-glibj=build"
+ac_configure_args="$ac_configure_args --disable-plugin"
if test "$use_gtk_awt" != yes; then
ac_configure_args="$ac_configure_args --disable-gtk-peer"
fi
@@ -676,21 +677,6 @@
AC_PATH_XTRA
-# determine whether to enable the cairo GTK Graphics2D backend
-AC_ARG_ENABLE(gtk-cairo,
- AS_HELP_STRING([--enable-gtk-cairo],
- [build the cairo Graphics2D implementation on GTK]))
-AM_CONDITIONAL(GTK_CAIRO, test "x${enable_gtk_cairo}" = xyes)
-if test "x${enable_gtk_cairo}" = xyes
-then
- PKG_CHECK_MODULES(CAIRO, cairo)
- PKG_CHECK_MODULES(PANGOFT2, pangoft2)
-fi
-AC_SUBST(CAIRO_LIBS)
-AC_SUBST(CAIRO_CFLAGS)
-AC_SUBST(PANGOFT2_LIBS)
-AC_SUBST(PANGOFT2_CFLAGS)
-
# FIXME: this should be _libs on some hosts.
libsubdir=.libs
Index: ChangeLog
===
--- ChangeLog (revision 114539)
+++ ChangeLog (working copy)
@@ -1,3 +1,8 @@
+2006-06-10 Thomas Fitzsimmons <[EMAIL PROTECTED]>
+
+ * configure.ac (ac_configure_args): Add --disable-plugin.
+ * configure: Regenerate.
+
2006-06-09 Tom Tromey <[EMAIL PROTECTED]>
PR libgcj/27730:
RE: Errors while building bootstrap GCC for "mipsisa32-elf" target
Thanks for the reply. I have tried this but when I check out GCC source using SVN, It is 1.38 GB. I have space problem on my system so it is difficult to check out all supported tool sources and make combined tree. I am not able to understand, why the checkout source of GCC is so large in size? I am using the following command to checkout source: "svn checkout svn://gcc.gnu.org/svn/gcc/trunk gcc" Can I use gcc4.1.1 instead of checkout GCC source to make the combined tree? > -Original Message- > From: Eric Christopher [mailto:[EMAIL PROTECTED] > > > Hi all, > > > > I am new to this list and GCC compiler. I am trying to build > > GCC4.1.0 for > > "mipsisa32-elf" target. I would appreciate if someone could help me > > out in > > resolving the errors during build process. > > You should really use a combined tree for this. There are also docs > on the web page on how to build a cross toolchain: > > http://gcc.gnu.org/simtest-howto.html > > -eric
Re: Errors while building bootstrap GCC for "mipsisa32-elf" target
On Jun 10, 2006, at 12:30 AM, Monika Sapra wrote:
Thanks for the reply. I have tried this but when I check out GCC
source
using SVN, It is 1.38 GB. I have space problem on my system so it is
difficult to check out all supported tool sources and make combined
tree.
Ha, that's nothing, you should try building it:
mrs $ du -H -s ../gcc-darwin
3289224 ../gcc-darwin
Anyway, this is the wrong list to pursue disk space expansions.
Personally, I'd recommend the 500 GB Seagate drive for US$189. This
is also the wrong list to use for all questions about gcc. gcc-help
is a better place.
I am not able to understand, why the checkout source of GCC is so
large in
size?
rm -rf gcc/{java,ada,testsuite,cp,fortran} lib
{java,ada,fortran,stdc++}
if you don't need them, that should save some space.
Re: GIMPLE / induction variable analysis
Hello, > I'm looking for an induction variable analysis which will operate at the > GIMPLE level. So far, I've found... > > loop-iv.c -- RTL induction variable analysis > tree-ssa-loop-ivopts.c -- GIMPLE induction variable analysis no, tree-level induction variable analysis is in tree-scalar-evolution.c. What you are looking for most likely is simple_iv function (or if you are adventurous and want to handle non-affine induction variables or evolutions in several loops at once as well, analyze_scalar_evolution and instantiate_parameters functions). Zdenek > The latter appears to be the right choice but nearly all of the > functions - and certainly the key data structures - are placed in the .c > file, hidden away from the outside world. > > Is there a reason that this interface hasn't been exposed in a header > file? I can certainly duplicate the interface into a header - for > private development purposes - but if there's a good reason not do this, > is there a better approach? > > Thanks, > > -- > Jay L.T. Cornwall, http://www.esuna.co.uk/~jay/ > PhD Student > Imperial College London
Re: Errors while building bootstrap GCC for "mipsisa32-elf" target
"Monika Sapra" <[EMAIL PROTECTED]> writes: > Thanks for the reply. I have tried this but when I check out GCC source > using SVN, It is 1.38 GB. Try upgrading subversion. With version 1.3+, the checked out tree is only about half the size. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Re: GIMPLE / induction variable analysis
Hi, Thanks for your replies, scalar evolution is what I was looking for! -- Jay L.T. Cornwall, http://www.esuna.co.uk/~jay/ PhD Student Imperial College London
Re: bootstrap broken on PPC-darwin and other targets without pkg-config (which is almost all)
On Jun 10, 2006, at 12:23 AM, Thomas Fitzsimmons wrote: Andrew Pinski wrote: Caused by: http://gcc.gnu.org/ml/gcc-cvs/2006-06/msg00225.html I committed this fix. Did you know trunk of GCC is in release branch and has been since Thursday? -- Pinski
Re: bootstrap broken on PPC-darwin and other targets without pkg-config (which is almost all)
Andrew, What is the release branch called? I can't get anything pulled down with... svn co svn://gcc.gnu.org/svn/gcc/branches/gcc-4_2-branch gcc Our isn't it in the svn repository yet. Jack
Re: bootstrap broken on PPC-darwin and other targets without pkg-config (which is almost all)
On Jun 10, 2006, at 9:03 AM, Jack Howarth wrote: Andrew, What is the release branch called? I can't get anything pulled down with... There is no release branch but the release branch rules are in effect on the mainline (trunk). See http://gcc.gnu.org/ml/gcc/2006-06/msg00120.html -- Pinski
Re: bootstrap broken on PPC-darwin and other targets without pkg-config (which is almost all)
Andrew Pinski writes: > > On Jun 10, 2006, at 9:03 AM, Jack Howarth wrote: > > > Andrew, > > What is the release branch called? I can't get anything pulled > > down with... > > There is no release branch but the release branch rules are in effect > on the mainline (trunk). > > See http://gcc.gnu.org/ml/gcc/2006-06/msg00120.html I imagine that many people missed that announcement. I certainly did. Whilst I greatly appreciate Mark's GCC 4.2 Status Reports, I don't always read them all. Andrew.
gcc-4.2-20060610 is now available
Snapshot gcc-4.2-20060610 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.2-20060610/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.2 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision 114541 You'll find: gcc-4.2-20060610.tar.bz2 Complete GCC (includes all of below) gcc-core-4.2-20060610.tar.bz2 C front end and core compiler gcc-ada-4.2-20060610.tar.bz2 Ada front end and runtime gcc-fortran-4.2-20060610.tar.bz2 Fortran front end and runtime gcc-g++-4.2-20060610.tar.bz2 C++ front end and runtime gcc-java-4.2-20060610.tar.bz2 Java front end and runtime gcc-objc-4.2-20060610.tar.bz2 Objective-C front end and runtime gcc-testsuite-4.2-20060610.tar.bz2The GCC testsuite Diffs from 4.2-20060603 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.2 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
Re: Some C++0x experiments
On Jun 9, 2006, at 9:31 PM, Pedro Lamarão wrote: Any feedback is welcome! Thank you! -Howard
Re: Highlevel C Backend
> One imagines that one would construct a virtual machine architecture > framework gcc already has one. It's called RTL. > and then write a back-end that would generate "machine code" for > that virtual machine, which would be a subset of ANSI C. Hey-presto, you > then have a butt-ugly anything-to-ANSI-C translator, that (whoops) loses > any > back-end-specific > optimizations. Treating C like an overgrown assembly language is certainly possible. Whether there's any benefit in doing that compared to writing a proper backend for whatever cpu you're interested in, or emulating a common/simple cpu, is a completely different question. Maintaining a gcc backend of any type is a significant undertaking. Maintaining a backend for an abnormal target (eg. C source) that's unlikely to ever be accepted into mainstream sourced is even more so. Paul
Re: Wconversion versus Wcoercion
On 09/06/06, Eric Christopher <[EMAIL PROTECTED]> wrote: I think I like b) the most. That way people who are accustomed to using -Wconversion for value conversions can continue doing so and we can move to something like -Wprototype-conversion or something for the other (and stick the second in -Wall and have -Wconversion be outside of that perhaps... that'd be up to others to debate though). That would be fine with me. However, using Wconversion for value conversions is not the documented purpose. There are several emails and replies in bugzilla stating that Wconversion has one specific purpose and it should not be used for anything else. If there has been a decision to change this, I have not been able to find it in the mailing list archive. I would like to know if there is someone against moving the original purpose of Wconversion to a different option like Wprototype-missing-conversion or Wtraditional-conversion. On the other hand, it is true that more and more undocumented "value conversion" features have been added to Wconversion. Even if you don't like to change the documented behaviour, the reality is that the change is already there, it is just that the docs are outdated. Wcoercion + Wconversion : 0 votes Wconversion + Wprototype-missing-conversion: 1 (Eric) votes Cheers, Manuel.
Re: Wconversion versus Wcoercion
On Jun 10, 2006, at 1:30 PM, Manuel López-Ibáñez wrote: On 09/06/06, Eric Christopher <[EMAIL PROTECTED]> wrote: I think I like b) the most. That way people who are accustomed to using -Wconversion for value conversions can continue doing so and we can move to something like -Wprototype-conversion or something for the other (and stick the second in -Wall and have -Wconversion be outside of that perhaps... that'd be up to others to debate though). That would be fine with me. Here is my vote, have four options: -Wconversion the same as now. -Wprototype-conversion turns on part of -Wconversion -Wcoercion the option you are dealing with -Wconversion-signed the other part of the doc for -Wconversion -- Pinski
Re: [wwwdocs] Complete revamp of our web site
On Tue, 6 Jun 2006, Joe Buck wrote: >> Also what about moving the News up to a noticeable spot since right now >> it is down in a corner so it looks out of place. In fact on my screen >> which is set to 1024x768, I have to scroll to get to the news. > Yes, the top news needs to be on the front page, anything you have to > scroll down for effectively isn't on the front page. On those systems I tested, include my notebook, things fit nicely in one window (basically no scrolling), both before the revamp and thereafter (this part wasn't really affected by the revamp). This is good feedback, though. Apparently this affects many users out there, so let me see what I can do about it. Gerald
Re: [wwwdocs] Complete revamp of our web site
On Sat, 10 Jun 2006, Andrew Pinski wrote: > Attach is what I see currently on the web page, the news is down low in the > lower right. > Barely noticeable. Ack. Would you mind sending another screenshot tomorrow evening your time? ;-) Gerald
Re: Wconversion versus Wcoercion
"Manuel López-Ibáñez" <[EMAIL PROTECTED]> writes: [...] | (b) keep the warnings of conversions that may change a value in | Wconversion and move its original purpose (the warnings about | prototypes causing ... in the absence of a prototype) to a new option | (suggestions are welcome). I prefer this. I'll like to see a more precise definition of your understanding of "coercion" versus "conversion". Last time we dicussed this I was not quite clear about what you consider is "bad" what is not. I was under the impression you taught it was for "C" only, but you have to take into account that some warnings are shared with the C++ front-end and some of them really should be common to both front-ends. If your project is NOT about coercion in general, but those just related to function prototypes, you should be careful about the name of the option. Again, this assumes you tell us what you consider coercion and what you consider conversion. -- Gaby
