public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dominik Vogt <vogt@linux.vnet.ibm.com>
To: gcc-patches@gcc.gnu.org
Cc: gofrontend-dev@googlegroups.com
Subject: [PATCH 2/9] Gccgo port to s390[x] -- part I
Date: Tue, 09 Sep 2014 12:49:00 -0000	[thread overview]
Message-ID: <20140909124942.GC25290@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140909124446.GA25290@linux.vnet.ibm.com>

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

A test case added to golang for the previous patch.

gcc/testsuite/ChangeLog
2014-09-05  Dominik Vogt  <vogt@linux.vnet.ibm.com>

        * go.test/test/recover.go (test1): Test recover() from deferred
        recursive function.

Ciao

Dominik ^_^  ^_^

-- 

Dominik Vogt
IBM Germany

[-- Attachment #2: 0002-TEST-Add-a-recover-test.patch --]
[-- Type: text/x-diff, Size: 1087 bytes --]

From a3cc3d043d580d083f5dd573cb66d299cd985604 Mon Sep 17 00:00:00 2001
From: Dominik Vogt <vogt@linux.vnet.ibm.com>
Date: Tue, 9 Sep 2014 09:30:09 +0100
Subject: [PATCH 2/9] TEST: Add a recover test.

---
 gcc/testsuite/go.test/test/recover.go | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/gcc/testsuite/go.test/test/recover.go b/gcc/testsuite/go.test/test/recover.go
index 071be66..b31b5ac 100644
--- a/gcc/testsuite/go.test/test/recover.go
+++ b/gcc/testsuite/go.test/test/recover.go
@@ -113,10 +113,23 @@ func withoutRecover() {
 	mustNotRecover() // because it's a sub-call
 }
 
+func withoutRecoverRecursive(n int) {
+	if (n == 0) {
+		withoutRecoverRecursive(1)
+	} else {
+		v := recover()
+		if v != nil {
+			println("spurious recover (recursive)", v)
+			die()
+		}
+	}
+}
+
 func test1() {
 	defer mustNotRecover() // because mustRecover will squelch it
 	defer mustRecover(1)   // because of panic below
 	defer withoutRecover() // should be no-op, leaving for mustRecover to find
+	defer withoutRecoverRecursive(0) // ditto
 	panic(1)
 }
 
-- 
1.8.4.2


  parent reply	other threads:[~2014-09-09 12:49 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09 12:44 [PATCH 0/9] " Dominik Vogt
2014-09-09 12:48 ` [PATCH 1/9] " Dominik Vogt
2014-09-09 12:49 ` Dominik Vogt [this message]
2014-10-09 18:56   ` [gofrontend-dev] [PATCH 2/9] " Ian Lance Taylor
2014-09-09 12:51 ` [PATCH 3/9] " Dominik Vogt
2014-10-03 18:28   ` [gofrontend-dev] " Ian Lance Taylor
2014-09-09 12:53 ` [PATCH 4/9] " Dominik Vogt
2014-10-04  1:19   ` [gofrontend-dev] " Ian Lance Taylor
2014-10-06  6:52     ` Dominik Vogt
2014-09-09 12:56 ` [PATCH 5/9] " Dominik Vogt
2014-10-04  1:26   ` [gofrontend-dev] " Ian Lance Taylor
2014-10-06  7:42     ` Dominik Vogt
2014-10-06 14:29       ` Ian Lance Taylor
2014-10-07 10:45         ` Dominik Vogt
2014-10-09 20:07           ` Ian Lance Taylor
2014-09-09 12:58 ` [PATCH 6/9] " Dominik Vogt
2014-10-16 22:59   ` [gofrontend-dev] " Ian Lance Taylor
2014-09-09 13:02 ` [PATCH 7/9] " Dominik Vogt
2014-10-16 23:46   ` [gofrontend-dev] " Ian Lance Taylor
2014-10-28 14:40     ` Dominik Vogt
2014-10-28 17:37       ` Ian Taylor
2014-10-29  9:05         ` Dominik Vogt
2014-10-29 16:43   ` Andreas Schwab
2014-10-29 16:43     ` [gofrontend-dev] " Ian Taylor
2014-10-29 17:05       ` Andreas Schwab
2014-10-29 17:50         ` Ian Taylor
2014-10-30  7:50           ` Dominik Vogt
2014-10-30 15:05             ` Ian Taylor
2014-10-31  9:30               ` Dominik Vogt
2014-10-31 16:50                 ` Ian Taylor
2014-10-30 21:57             ` Joseph S. Myers
2014-09-09 13:04 ` [PATCH 8/9] " Dominik Vogt
2014-10-17  0:03   ` [gofrontend-dev] " Ian Lance Taylor
2014-10-29  9:13     ` Dominik Vogt
2014-10-29 15:22       ` Ian Taylor
2014-09-09 13:06 ` [PATCH 9/9] " Dominik Vogt
2014-10-17  0:07   ` [gofrontend-dev] " Ian Lance Taylor
2014-10-17  0:45 ` [gofrontend-dev] [PATCH 0/9] " Ian Lance Taylor

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=20140909124942.GC25290@linux.vnet.ibm.com \
    --to=vogt@linux.vnet.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gofrontend-dev@googlegroups.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 read-only IMAP folder(s) and NNTP newsgroup(s).