On 10/06/2014 06:57 PM, Eric Botcazou wrote:
I posted it with v2 in the subject. I have now attached it.
There is a pasto in the v2:
@@ -1764,6 +1772,12 @@ extern int sparc_indent_opcode;
#define AS_LEON_FLAG -Av8
#endif
+#ifdef HAVE_AS_LEONV7
+#define AS_LEONV7_FLAG -Aleon
+#else
You're right. I have attached an updated patch. The new code becomes:
#ifdef HAVE_AS_LEON
#define AS_LEON_FLAG -Aleon
+#define AS_LEONV7_FLAG -Aleon
#else
#define AS_LEON_FLAG -Av8
+#define AS_LEONV7_FLAG -Av7
#endif
The patch is OK for all active branches (trunk, 4.9 and
On 10/07/2014 09:26 AM, Eric Botcazou wrote:
You're right. I have attached an updated patch. The new code becomes:
#ifdef HAVE_AS_LEON
#define AS_LEON_FLAG -Aleon
+#define AS_LEONV7_FLAG -Aleon
#else
#define AS_LEON_FLAG -Av8
+#define AS_LEONV7_FLAG -Av7
#endif
The patch is OK
Ok, I will update that. Is there a way of generating the comments
automatically?
Do you mean the ChangeLog? If so, contrib/mklog will generate a skeleton but
you'll still need to write the decription sentences.
--
Eric Botcazou
On 10/07/2014 11:07 AM, Eric Botcazou wrote:
Ok, I will update that. Is there a way of generating the comments
automatically?
Do you mean the ChangeLog? If so, contrib/mklog will generate a skeleton but
you'll still need to write the decription sentences.
Perfect, thanks!
I have sent an updated patch just now. In case -Aleon does not exist it
should select -Av7 instead of -Av8.
No patch was attached to this message though.
Yes, we have. Just verified that with the FSF. It would be a nice for us to
have write access to the sparc parts.
OK, but the granularity
On 10/06/2014 10:40 AM, Eric Botcazou wrote:
I have sent an updated patch just now. In case -Aleon does not exist it
should select -Av7 instead of -Av8.
No patch was attached to this message though.
I posted it with v2 in the subject. I have now attached it.
Yes, we have. Just verified that
I posted it with v2 in the subject. I have now attached it.
There is a pasto in the v2:
@@ -1764,6 +1772,12 @@ extern int sparc_indent_opcode;
#define AS_LEON_FLAG -Av8
#endif
+#ifdef HAVE_AS_LEONV7
+#define AS_LEONV7_FLAG -Aleon
+#else
+#define AS_LEONV7_FLAG -Av7
+#endif
+
/* We use gcc
Hi,
On 10/02/2014 11:22 PM, Eric Botcazou wrote:
[Sorry for the long delay]
The LEON3/4 soft-core CPU has support for both SPARCv7 and SPARCv8 that
is configurable at design time. The majority of the LEON3 ASICs are v8
compatible, however when designing an as small LEON3 as possible, v7
[Sorry for the long delay]
The LEON3/4 soft-core CPU has support for both SPARCv7 and SPARCv8 that
is configurable at design time. The majority of the LEON3 ASICs are v8
compatible, however when designing an as small LEON3 as possible, v7
without FPU is frequently used.
The current GCC
Ping.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche
Hello,
what is the status for this patch?
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese
Hello,
I have not received any comments on the patch yet.
Eric, do you have any thoughts?
Best Regards,
Daniel Hellstrom
Software Section Head
Aeroflex Gaisler AB
Aeroflex Microelectronic Solutions – HiRel
Kungsgatan 12
SE-411 19 Gothenburg, Sweden
Phone: +46 31 7758657
dan...@gaisler.com
The LEON3/4 soft-core CPU has support for both SPARCv7 and SPARCv8 that
is configurable at design time. The majority of the LEON3 ASICs are v8
compatible, however when designing an as small LEON3 as possible, v7
without FPU is frequently used.
The current GCC leon3 support implies the SPARCv8
Daniel,
Does this mean that Sebastian's patch to add a leon3 multilib for
sparc-rtems
needs to be augmented to handled leon3v7? Or does it need to map to a
regular v7 library?
It just seems like the multilibs should have been touched somehow.
--joel
On 8/20/2014 10:01 AM, Daniel Hellstrom
Hi Joel,
Yes an update is required. If/when I get positive comments on the mcpu=leon3v7
patch I will suggest a new updated multilib patch and a RTEMS LEON3 BSP build
configuration change.
I have tested the mcpu=leon3v7 patch with RTEMS leon3 BSP generating V7 instructions, and ngmp generating
16 matches
Mail list logo
