From: "Sysoltsev, Vyatcheslav" <vyatcheslav.sysoltsev@intel.com>
Cc: "Denis Briltz \(E-mail\)" <Denis.Briltz@intel.com>
Subject: FW: problem compiling guile on IA64 by Intel compiler
Date: Tue, 8 Jul 2003 19:46:20 +0400 [thread overview]
Message-ID: <67B5ACB373D0D411B9BD00508BD951A7032E46A3@nnsmsx30.inn.intel.com> (raw)
I expect some reply to ensure that this is not dummy mailbox.
--Slava
-----Original Message-----
From: Sysoltsev, Vyatcheslav
Sent: Tuesday, June 24, 2003 4:45 PM
To: 'bug-guile@gnu.org'
Cc: Denis Briltz (E-mail)
Subject: problem compiling guile on IA64 by Intel compiler
Hi there!
Because Intel compiler doesn't support asm inlines on IA64 I cannot compile
guile from sources on IA64 due to SCM_FENCE macro from libguile/__scm.h.
Here is this macro:
/* Anthony Green writes:
When the compiler sees...
DEFER_INTS;
[critical code here]
ALLOW_INTS;
...it doesn't actually promise to keep the critical code within the
boundries of the DEFER/ALLOW_INTS instructions. It may very well
schedule it outside of the magic defined in those macros.
However, GCC's volatile asm feature forms a barrier over which code is
never moved. So if you add...
asm ("");
...to each of the DEFER_INTS and ALLOW_INTS macros, the critical
code will always remain in place. asm's without inputs or outputs
are implicitly volatile. */
#ifdef __GNUC__
#define SCM_FENCE asm /* volatile */ ("")
#else
#define SCM_FENCE
#endif
So I'd change the condition
#ifdef __GNUC__
... to ...
#if defined(__GNUC__) && !(defined(__INTEL_COMPILER) && defined(__ia64))
In this case the code will be acceptable both with gcc and Intel compiler.
However as I understand from the comment defining SCM_FENCE to nothing is
dangerous because of the compiler optimization. If you've got a real problem
with it, let me know and I will cope with this further.
-- Slava Sysoltsev
----------------------------------------------------------------------------
----------------------
--- libguile/__scm.h.orig 2003-06-24 16:33:40.000000000 +0400
+++ libguile/__scm.h 2003-06-24 16:34:35.000000000 +0400
@@ -362,7 +362,7 @@
...to each of the DEFER_INTS and ALLOW_INTS macros, the critical
code will always remain in place. asm's without inputs or outputs
are implicitly volatile. */
-#ifdef __GNUC__
+#if defined(__GNUC__) && !(defined(__INTEL_COMPILER) && defined(__ia64))
#define SCM_FENCE asm /* volatile */ ("")
#else
#define SCM_FENCE
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2003-07-08 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 15:46 Sysoltsev, Vyatcheslav [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-09 5:03 FW: problem compiling guile on IA64 by Intel compiler Sysoltsev, Vyatcheslav
2003-07-09 9:44 ` Thien-Thi Nguyen
2003-07-09 9:49 Sysoltsev, Vyatcheslav
2003-07-09 10:24 ` Thien-Thi Nguyen
2003-07-09 12:23 Sysoltsev, Vyatcheslav
2003-07-09 14:26 ` Thien-Thi Nguyen
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=67B5ACB373D0D411B9BD00508BD951A7032E46A3@nnsmsx30.inn.intel.com \
--to=vyatcheslav.sysoltsev@intel.com \
--cc=Denis.Briltz@intel.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).