From: "Richard W.M. Jones" <rich@annexia.org>
To: Dmitry Bely <dmitry.bely@gmail.com>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Interfacing with C: bad practice
Date: Tue, 16 Aug 2011 17:22:05 +0100 [thread overview]
Message-ID: <20110816162205.GC31932@annexia.org> (raw)
In-Reply-To: <CAMT7qiSATQcrziJNLp8U=Lwtaj78HFdhgiRd34qJCJOurK0s-g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
On Tue, Aug 16, 2011 at 08:18:48PM +0400, Dmitry Bely wrote:
> On Tue, Aug 16, 2011 at 8:10 PM, Richard W.M. Jones <rich@annexia.org> wrote:
>
> > Well it would certainly help if we had a piece of runnable code to
> > look at. The code supplied in the original email contains an infinite
> > loop.
>
> Yes, that was my mistake that I corrected later. The loop should be
>
> for (; *s != NULL; s++) {
> list = wrp_ml_cons(caml_copy_string(*s), list); /* bug! */
> }
Well, contrary to what I said earlier, it really does seem
like this is undefined C behaviour.
Try the attached program, which distills the problem down to something
simple. gcc with -O0 and -O2 produces completely different answers,
and the assembler output confirms it.
Rich.
--
Richard Jones
Red Hat
[-- Attachment #2: test.c --]
[-- Type: text/x-csrc, Size: 332 bytes --]
#include <stdio.h>
#include <stdlib.h>
void f (int a, int b);
int g (void);
int *global = NULL;
int
main (void)
{
int x = 1;
global = &x;
f (g (), x);
exit (0);
}
void
f (int a, int b)
{
printf ("a = %d, b = %d\n", a, b);
}
int
g (void)
{
if (global) {
global++;
return *global;
}
else
return 42;
}
next prev parent reply other threads:[~2011-08-16 16:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 7:37 Dmitry Bely
2011-08-16 8:04 ` Török Edwin
2011-08-16 8:25 ` Dmitry Bely
2011-08-16 8:43 ` Török Edwin
2011-08-16 9:46 ` rixed
2011-08-16 9:53 ` Dmitry Bely
2011-08-16 10:17 ` Török Edwin
2011-08-16 11:04 ` rixed
[not found] ` <20110816.105738.246515733851238101.Christophe.Troestler@umons.ac.be>
2011-08-16 9:21 ` Dmitry Bely
2011-08-16 10:39 ` Mauricio Fernandez
2011-08-16 14:27 ` John Carr
2011-08-16 12:28 ` [Caml-list] " Dmitry Bely
2011-08-16 15:25 ` [Caml-list] " Richard W.M. Jones
2011-08-16 15:51 ` rixed
2011-08-16 16:00 ` Will M. Farr
2011-08-16 16:10 ` Richard W.M. Jones
2011-08-16 16:17 ` Richard W.M. Jones
2011-08-16 16:18 ` Dmitry Bely
2011-08-16 16:22 ` Richard W.M. Jones [this message]
2011-08-16 16:27 ` Richard W.M. Jones
2011-08-16 16:30 ` malc
2011-08-16 16:34 ` Török Edwin
2011-08-16 16:47 ` Richard W.M. Jones
2011-08-16 16:55 ` [Caml-list] " Jeffrey Scofield
2011-08-16 17:08 ` Will M. Farr
2011-08-16 19:46 ` Gerd Stolpmann
2011-08-16 20:18 ` Jeffrey Scofield
2011-08-16 17:08 ` [Caml-list] " rixed
2011-08-16 16:06 ` John Carr
2011-08-16 16:14 ` Wojciech Meyer
2011-08-16 16:13 ` Dmitry Bely
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110816162205.GC31932@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=dmitry.bely@gmail.com \
/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