From: Rieger, David <david.rieger@student.kit.edu>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] Clang does not understand .word directive in crt0.S in newlib source
Date: Mon, 16 Jan 2017 11:24:50 +0000 [thread overview]
Message-ID: <bc71a06a3bf94b40b2adcdc8f816199f@kit-msx-25.kit.edu> (raw)
Hello everyone
I am trying to compile newlib using clang/LLVM 3.8.1 with the or1k target. However, compilation fails on newlib-source/libgloss/or1k/crt0.S with clang complaining it does not know the ".word" assembler directive:
../newlib-source/libgloss/or1k/crt0.S:83:19: error: unknown directive
_or1k_stack_size: .word 8192
^
../newlib-source/libgloss/or1k/crt0.S:84:29: error: unknown directive
_or1k_exception_stack_size: .word 8192
Any help in how I can fix this so clang compiles the file would be greatly appreciated.
Thanks
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20170116/d656ec45/attachment.html>
next reply other threads:[~2017-01-16 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 11:24 Rieger, David [this message]
2017-01-16 13:44 ` [OpenRISC] Clang does not understand .word directive in crt0.S in newlib source Rieger, David
2017-01-16 14:08 ` Jeremy Bennett
2017-01-16 15:50 ` Rieger, David
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=bc71a06a3bf94b40b2adcdc8f816199f@kit-msx-25.kit.edu \
--to=david.rieger@student.kit.edu \
--cc=openrisc@lists.librecores.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.