From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Compiling 1.7.0 with gcc-3.3
Date: Mon, 19 May 2003 09:26:30 -0500 [thread overview]
Message-ID: <87el2vovvt.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <E19Hhab-0000es-00@witch> (Mikael Djurfeldt's message of "Mon, 19 May 2003 12:09:53 +0200")
Mikael Djurfeldt <mdj@kvast.blakulla.net> writes:
> Of course, I'd like this to work with the default
> --enable-error-on-warning. However, there are two problematic
> instances. One is the use of SCM_STACKITEM. For example:
>
> eval.c:1965:
> if (scm_stack_checking_enabled_p
> && SCM_STACK_OVERFLOW_P ((SCM_STACKITEM *) &proc))
Right I posted this to guile-devel a week or so ago. Someone posted a
(void *) coercion fix, but I haven't had a chance to look in to it.
> This could be "solved" by adding -Wno-strict-aliasing to the
> compilation options, but that might remove better motivated warnings.
I'd be happier with -fno-strict-aliasing, but I don't really want that
either. I'd rather see if we can alter the code to avoid the warning.
> I think this is a stupid warning message. In any case, you'd want to
> be able to shut it off. I can't find any way to do that. Maybe we
> should talk to the gcc people about this?
>
> I've tried to enclose the code causing the warning with a surrounding
> conditional which tests the sizes of the data types, but the compiler
> outputs the above warning even though the code isn't going to be
> compiled.
We've worked around a bunch of warnings of this type before (I think
Marius fixed most of them), so hopefully we can just adjust the code
to avoid these too.
> I think it's important to resolve this in some way. If we can't, I'm
> going to suggest that we shut off error-on-warning as a default, which
> would be sad. But Guile should compile "out-of-the-box".
I'd be strongly opposed to turning off -Werror. I'd like to consider
that a last resort.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-19 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 10:09 Compiling 1.7.0 with gcc-3.3 Mikael Djurfeldt
2003-05-19 14:26 ` Rob Browning [this message]
2003-05-19 17:05 ` Bruce Korb
2003-05-22 10:26 ` Mikael Djurfeldt
2003-05-19 16:20 ` Bruce Korb
2003-05-22 9:37 ` Mikael Djurfeldt
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87el2vovvt.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-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.
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).