From: "Ralf Wildenhues" <Ralf.Wildenhues@gmx.de>
To: Jie Liu <lj8175@gmail.com>
Cc: Andrew Haley <aph@redhat.com>,
java-patches@gcc.gnu.org, java@gcc.gnu.org,
gcc-patches@gcc.gnu.org,
Joel Sherrill <joel.sherrill@oarcorp.com>
Subject: Re: [PATCH] [JAVA] patch for Java on RTEMS
Date: Fri, 26 Aug 2011 13:20:00 -0000 [thread overview]
Message-ID: <20110826131955.22020@gmx.net> (raw)
In-Reply-To: <CABc96T_xe41pdHOBJDMvExbkbUrs9NknOT9-Lj1aDUEB6-sQBQ@mail.gmail.com>
* Jie Liu wrote on Mon, Aug 15, 2011 at 04:07:36PM CEST:
> > Looks OK, but there is no ChangeLog. Â Do you have copyright
> > assignment?
>
> Have added ChangeLog to the patch, please see the attachment. And I
> think I have copyright assignment, because I have Free Software
> Foundation paperwork, as "ASSIGNMENT - GNU GCC ... JIE RT688742"
The build-system specific parts of the patch are OK, provided
that they have been sufficiently tested. When committing
top-level changes, please make sure they are synced to the
src repository; if you don't have write access to src, please
ask someone who has to do that for you.
I think you still need approval for the boehm-gc related changes.
Please also try to send patches with some text MIME type.
Thanks,
Ralf
> --- boehm-gc/ChangeLog (revision 172224)
> +++ boehm-gc/ChangeLog (working copy)
> @@ -1,3 +1,22 @@
> +2011-08-15 Jie Liu <lj8175@gmail.com>
> + * configure.ac: Add configure for RTEMS.
> + * configure: Add configure for RTEMS.
> + * include/gc_config.h.in: Add GC_RTEMS_PTHREADS for RTEMS.
> + * mach_dep.c (GC_with_callee_saves_pushed): Use setjmp for
> + RTEMS.
> + * include/gc_config_macros.h: Define GC_PTHREADS for rtems.
> + * include/private/gcconfig.h: Add configure for RTEMS/i386;
> + Use calloc for RTEMS to GET_MEM.
> + * pthread_stop_world.c (GC_stop_init): Add judge SA_RESTART
> + for operating system; Use sigprocmask unblock the signal
> + for RTEMS.
> + * pthread_support.c: Define USE_PTHREAD_SPECIFIC for RTEMS;
> + Do not include sys/mman.h for RTEMS; Add default GC_nprocs
> + for RTEMS.
> + * gc_dlopen.c: Do not include dlfcn.h for RTEMS.
> + * os_dep.c: Do not use auxiliary routines for obtaining
> + memory from RTEMS.
> --- ChangeLog (revision 172224)
> +++ ChangeLog (working copy)
> @@ -1,3 +1,8 @@
> +2011-08-15 Jie Liu <lj8175@gmail.com>
> +
> + * configure.ac (*-*-rtems*): Remove ${libgcj} in nonconfigdirs.
> + * configure: Regenerate.
> --- libjava/ChangeLog (revision 172224)
> +++ libjava/ChangeLog (working copy)
> @@ -1,3 +1,13 @@
> +2011-08-15 Jie Liu <lj8175@gmail.com>
> +
> + * configure.ac (THREADS): Add configuration for RTEMS.
> + * configure.host (host): Add configuration for RTEMS.
> + * include/config.h.in: Add RTEMS_PTHREADS for RTEMS.
> + * configure: Add configure for RTEMS.
> + * classpath/native/fdlibm/mprec.c: Remove _mprec_log10 for RTEMS.
> + * posix-threads.cc: Use SIGHUP for INTR on RTEMS.
> + * java/lang/natClass.cc: Undef HAVE_TLS for RTEMS.
prev parent reply other threads:[~2011-08-26 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 17:00 Jie Liu
2011-08-14 13:04 ` Jie Liu
2011-08-26 13:33 ` Ralf Corsepius
2011-08-15 9:43 ` Andrew Haley
2011-08-15 14:07 ` Jie Liu
2011-08-15 14:11 ` Andrew Haley
2011-08-26 13:20 ` Ralf Wildenhues [this message]
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=20110826131955.22020@gmx.net \
--to=ralf.wildenhues@gmx.de \
--cc=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=joel.sherrill@oarcorp.com \
--cc=lj8175@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 read-only IMAP folder(s) and NNTP newsgroup(s).