From: oleg@okmij.org
To: Evgeny Khramtsov <xramtsov@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Delimcc bug
Date: Fri, 2 Jun 2017 11:05:57 -0400 [thread overview]
Message-ID: <20170602150557.GA91690@www1.g3.pair.com> (raw)
In-Reply-To: <20170602173221.0583a14c@zinid.ru>
On Fri, Jun 02, 2017 at 05:32:21PM +0300, Evgeny Khramtsov wrote:
> Does anyone know where to report bugs in Delimcc?
> Is it even supported?
> Under some conditions I have segfaults in it when compiled natively in
> 4.04.1.
>
You can send me directly, or send to the list if you want. But be sure
you fetch the latest version from my web page. The problem is usually
GCC, which optimizes too much. So, special flags are required to switch
off some optmizations. You can see in the Makefile. If you have a very
recent version of GCC, chances are it needs some more flags to disable
too aggressive optimizations.
next prev parent reply other threads:[~2017-06-02 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 14:32 Evgeny Khramtsov
2017-06-02 15:05 ` oleg [this message]
2017-06-02 15:31 ` Ivan Gotovchits
2017-06-02 15:52 ` Evgeny Khramtsov
2017-06-03 5:26 ` Evgeny Khramtsov
2017-06-03 9:08 ` Jeremy Yallop
2017-06-03 13:04 ` Evgeny Khramtsov
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=20170602150557.GA91690@www1.g3.pair.com \
--to=oleg@okmij.org \
--cc=caml-list@inria.fr \
--cc=xramtsov@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;
as well as URLs for NNTP newsgroup(s).