unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: [patch] combined build
Date: Thu, 15 Nov 2007 08:28:33 -0800	[thread overview]
Message-ID: <ur9hcjniiby.fsf@mothra.ics.uci.edu> (raw)
In-Reply-To: <473C347B.6080907@yandex.ru> (Dmitry Antipov's message of "Thu, 15 Nov 2007 14:58:51 +0300")

Dmitry Antipov <dmantipov@yandex.ru> writes:

  > This patch provides a minimal support for compiling (the most of) emacs C code at once using
  > -combine option supported by never versions of GCC. Since an almost everything is compiled
  > each time when the compiler is invoked, this mode is not suitable for developers. But it might
  > be useful for package builders and other peoples who just wants to do './configure && make &&
  > make install' sequence. This feature also gives GCC a chance to optimize something during
  > inter-module analysis.
  > 
  > Notes:
  > 
  > 1. Compiling with -combine implies quite strict function declarations vs. definitions checking,
  >    so C code is touched in some places. In particular, current 'fatal' implementation bombs
  >    out combining compilation, and I've redone it with va_args. This might be non-portable or
  >    may break some ancient compiler.

I went through exactly this exercise 2 years ago, trying to fix all the
combine problems in the tree at that time. I had to undo a similar
"fatal" change for these concerns.

Now is a good time to reconsider, IMHO we should not support building
without varargs.

Please note that to get the full benefit of interprocedural optimization
you'd also need -fwhole-program, and that implies that the files in
lwlib should be added to the temacs compile line.


  > 2. For me, it doesn't work when using GTK toolkit. When using both GTK and -combine, I've got
  >    the following nasty error messages:
  > 
  >    In file included from /usr/include/gtk-2.0/gtk/gtk.h:74,
  >                     from xterm.h:46,
  >                     from fns.c:53:
  >    /usr/include/gtk-2.0/gtk/gtkcurve.h:104: error: conflicting types for 'gtk_curve_get_vector'
  >    /usr/include/gtk-2.0/gtk/gtkcurve.h:104: error: previous declaration of 'gtk_curve_get_vector' was here
  >    /usr/include/gtk-2.0/gtk/gtkcurve.h:106: error: conflicting types for 'gtk_curve_set_vector'
  >    /usr/include/gtk-2.0/gtk/gtkcurve.h:106: error: previous declaration of 'gtk_curve_set_vector' was here
  > 
  >    I suspect this is a bug in GCC. So I've installed an additional check in configure.in
  >    to avoid using both GTK and -combine simultaneously.

What version of Gtk is this?
If you are certain this is a gcc bug, please report it.

  reply	other threads:[~2007-11-15 16:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 11:58 [patch] combined build Dmitry Antipov
2007-11-15 16:28 ` Dan Nicolaescu [this message]
2007-11-15 16:59   ` Stefan Monnier
2007-11-15 19:46     ` Dan Nicolaescu
2007-11-16  4:29     ` Richard Stallman
2007-11-16 11:11       ` Dmitry Antipov
2007-11-16 20:42       ` Dan Nicolaescu
2007-11-17 23:30         ` Richard Stallman
2007-11-16 10:46     ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ur9hcjniiby.fsf@mothra.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=dmantipov@yandex.ru \
    --cc=emacs-devel@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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).