caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rich@annexia.org>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: OCaML List Mailing <caml-list@inria.fr>
Subject: Re: [Caml-list] Trivial compiler patches
Date: Sat, 22 Mar 2014 07:15:08 +0000	[thread overview]
Message-ID: <20140322071508.GB10374@annexia.org> (raw)
In-Reply-To: <4C341FFE-FDF2-4EA3-B056-D4F658641E4C@math.nagoya-u.ac.jp>

[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]

On Sat, Mar 22, 2014 at 09:46:53AM +0900, Jacques Garrigue wrote:
> On 2014/03/22 07:28, Richard W.M. Jones wrote:
> > 
> > What's a good place to send trivial compiler patches?  I don't want to
> > open a new bug for what is essentially a one-line aarch64 fix.
> 
> You should. It would save you the time spent asking this question :-)
> More seriously, in theory all bug fixes should be tracked, even trivial
> ones, since it lets others know where they were fixed (and where not).

Let me tell you how ordinary open source projects operate.

(1) They use git.  No one uses svn.

(2) There is usually a mailing list where patches are posted,
discussed and refined.  For example:

https://lists.gnu.org/archive/html/qemu-devel/2014-03/threads.html

(3) There may be another path for trivial fixes to get into the
project, eg. for typos, obvious build fixes, whitespace changes and so
on.  In qemu this is:

http://wiki.qemu.org/Contribute/TrivialPatches
https://lists.nongnu.org/mailman/listinfo/qemu-trivial

This encourages people not to give up on simple fixes because of
excessive process.

(4) They use a decent bug tracking system (ie. not Mantis).

Rich.

-- 
Richard Jones
Red Hat

[-- Attachment #2: 0001-arm64-Trivial-fix-for-missing-parameter.patch --]
[-- Type: text/x-diff, Size: 832 bytes --]

From a2395eadd37ac467c5964d2cbabcbf32e1100110 Mon Sep 17 00:00:00 2001
From: "Richard W.M. Jones" <rjones@redhat.com>
Date: Sat, 22 Mar 2014 02:11:32 -0500
Subject: [PATCH] arm64: Trivial fix for missing parameter.

---
 asmcomp/arm64/emit.mlp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/asmcomp/arm64/emit.mlp b/asmcomp/arm64/emit.mlp
index 341812f..274e6ff 100644
--- a/asmcomp/arm64/emit.mlp
+++ b/asmcomp/arm64/emit.mlp
@@ -604,7 +604,7 @@ let emit_instr i =
         `	ldr	{emit_reg reg_trap_ptr}, [sp], 16\n`;
         cfi_adjust_cfa_offset (-16);
         stack_offset := !stack_offset - 16
-    | Lraise ->
+    | Lraise k ->
         begin match !Clflags.debug, k with
         | true, (Lambda.Raise_regular | Lambda.Raise_reraise) ->
           `	bl	{emit_symbol "caml_raise_exn"}\n`;
-- 
1.8.3.1


  reply	other threads:[~2014-03-22  7:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 22:28 Richard W.M. Jones
2014-03-22  0:46 ` Jacques Garrigue
2014-03-22  7:15   ` Richard W.M. Jones [this message]
2014-03-22  8:28     ` Gabriel Scherer
2014-03-25 15:49       ` Goswin von Brederlow
2014-03-25 16:01         ` Daniel Bünzli
2014-03-25 16:16         ` Richard W.M. Jones
2014-03-25 16:29           ` Anil Madhavapeddy
2014-03-27  9:34           ` Goswin von Brederlow
2014-03-27 11:22             ` Anil Madhavapeddy
2014-03-27 11:28               ` Thomas Gazagnaire
2014-03-27 12:23             ` François Bobot

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=20140322071508.GB10374@annexia.org \
    --to=rich@annexia.org \
    --cc=caml-list@inria.fr \
    --cc=garrigue@math.nagoya-u.ac.jp \
    /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).