Displaying 20 results from an estimated 600 matches similar to: "[LLVMdev] Modelling M68k registers?"
2010 Jul 31
1
Beginner setting up samba: NT_STATUS_LOGON_FAILURE
Hello,
I am trying to set up samba on this host and testing it locally
is giving me headaches right away.
tom at hversa:~:~$ smbclient -L localhost -U%
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.4.8]
Sharename Type Comment
--------- ---- -------
homes Disk Home Directories
print$ Disk Printer Drivers
2012 Dec 04
2
[LLVMdev] LLVM documentation work help
Sean,
I add the empty file .nojekyll to https://github.com/Jonathan2251/lbd/tree/gh-pages and do "make gh-pages" again. It's the same. I check the uvbook has the gh-pages as mine as follows,
https://github.com/nikhilm/uvbook/tree/gh-pages
https://github.com/Jonathan2251/lbd/tree/gh-pages
In addition to gh-pages, uvbook has the the other web site on
2012 Dec 04
2
[LLVMdev] LLVM documentation work help
Sean,
It is not work even though I change the PDF link as you indicated. I think I can just use directory/link https://github.com/Jonathan2251/lbd/tree/gh-pages instead http://jonathan2251.github.com/lbd/WriteAnLLVMBackendTutorialForCpu0.pdf as a work around solution. User can click the link and click left top button "ZIP" and get the epub and pdf.
Jonathan
--- 12/12/4 (二),Sean Silva
2012 Dec 04
0
[LLVMdev] LLVM documentation work help
You may need a ".nojekyll" file. uvbook has one <
https://github.com/nikhilm/uvbook/blob/gh-pages/.nojekyll>. Also see <
https://help.github.com/articles/files-that-start-with-an-underscore-are-missing
>.
Let me know if that doesn't work.
-- Sean Silva
On Mon, Dec 3, 2012 at 9:15 PM, gamma_chen <gamma_chen at yahoo.com.tw> wrote:
> Sean,
>
> I can
2012 Dec 04
0
[LLVMdev] LLVM documentation work help
Hi Jonathan,
sorry for the hijack. Can I help you writing the document?
Regards,
chenwj
On Tue, Dec 04, 2012 at 10:15:33AM +0800, gamma_chen wrote:
> Sean,
>
> I can create html, pdf and epub, then put them on
> <https://github.com/Jonathan2251/lbd/tree/gh-pages>.
> The uvbook example as below can click the pdf link and pop up a download window
> while I cannot. The
2012 Dec 04
5
[LLVMdev] LLVM documentation work help
Sean,
I can create html, pdf and epub, then put them on
<https://github.com/Jonathan2251/lbd/tree/gh-pages>.
The uvbook example as below can click the pdf link and pop up a download window while I cannot. The uvbook link is put on http://username.github.com/... while the "make gh-pages" put them on https://github.com/username/... How can I have the download link like uvbook
2012 Dec 04
1
[LLVMdev] LLVM documentation work help
Wei-Ren,
Sorry, currently, I have an English helper in documentation. The cpu0 is my brother teaching material for college, and I did llvm backend compiler tutorial for cpu0 since I didn't find a good tutorial in llvm backend design.
As I know, there are many way to contribute back to open source or llvm. For example, write qemu for cpu0 is a extended work in cpu0 llvm backend design. Or
1997 Sep 15
0
R-beta: R binaries for NEXTSTEP (I386 and M68k) on CRAN
Binary distributions of R-0.49 for NEXTSTEP (Intel and M68k) are now
available on CRAN:
http://www.ci.tuwien.ac.at/R/bin/i386-nextstep/R.0.49.I.b.tar.gz
http://www.ci.tuwien.ac.at/R/bin/m68k-nextstep/R.0.49.N.b.tar.gz
Because NEXTSTEP doesn't support dynamic loading, I've compiled
in a number of additional functions (mostly from the user contributed
section of CRAN) which I find
2006 May 05
0
[patch] m68k build crt0
found by Christian T. Steigies <cts@debian.org>
usr/klibc/arch/m68k/crt0.o: In function `_start':
usr/klibc/arch/m68k/crt0.S:(.text+0xe): undefined reference to `___libc_init'
too many '_'.
never seen jbsr, converted that to jsr.
Signed-off-by: maximilian attems <maks@sternwelten.at>
diff --git a/usr/klibc/arch/m68k/crt0.S b/usr/klibc/arch/m68k/crt0.S
index
2006 May 05
0
[patch] m68k archstat typo
found by Christian T. Steigies <cts@debian.org>
usr/include/arch/m68k/klibc/archstat.h:12: error: syntax error before '__dev64'
better use __stdev64 defined in klibc/stathelp.h
Signed-off-by: maximilian attems <maks@sternwelten.at>
diff --git a/usr/include/arch/m68k/klibc/archstat.h b/usr/include/arch/m68k/klibc/archstat.h
index 89c0341..dce25f9 100644
---
2014 Jan 15
0
[PATCH stable-only] virtio-net: fix build on m68k and sparc64
On Wed, Jan 15, 2014 at 9:26 AM, Michael S. Tsirkin <mst at redhat.com> wrote:
> As a result of backporting a bugfix, virtio_net started passing void *
> to page_address, assuming that it will get silently converted to struct
> page *. But this does not happen on architectures where page_address is
> a macro, the result is build failure as the macro tries to dereference
>
2014 Jan 15
0
[PATCH stable-only] virtio-net: fix build on m68k and sparc64
On Wed, Jan 15, 2014 at 9:46 AM, Michael S. Tsirkin <mst at redhat.com> wrote:
> On Wed, Jan 15, 2014 at 09:36:13AM +0100, Geert Uytterhoeven wrote:
>> On Wed, Jan 15, 2014 at 9:26 AM, Michael S. Tsirkin <mst at redhat.com> wrote:
>> > As a result of backporting a bugfix, virtio_net started passing void *
>> > to page_address, assuming that it will get
2009 Apr 25
0
[LLVMdev] m68k backend
I have a few weeks of downtime between jobs coming up and I was considering
trying to put together a m68k backend for LLVM. I have some experience with
compiler front ends; I've maintained a couple of DSL implementations in the
past, but I have relativly little knowledge of code generation. I know that
there have been a few attempts in the past, but I cannot find any evidence
that they made
2009 Apr 25
0
[LLVMdev] m68k backend
Hello Kenneth,
I don't know of any 68k backend and would certainly appreciate it if somebody took up the task! I'm working on a frontend for compatibility with the old Amos BASIC on the Amiga and was going to have to start a new backend for the classic models.
That being said, I don't think 3 or 4 weeks would be enough unless you're really good with both 68k Assembly and
2003 Sep 25
1
[Bug 718] Compilation error on m68k-next-openstep 4.0
http://bugzilla.mindrot.org/show_bug.cgi?id=718
Summary: Compilation error on m68k-next-openstep 4.0
Product: Portable OpenSSH
Version: 3.6.1p2
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P1
Component: Build system
AssignedTo: openssh-bugs at mindrot.org
2016 Jun 02
0
[RFC v3 29/45] m68k: dma-mapping: Use unsigned long for dma_attrs
Split out subsystem specific changes for easier reviews. This will be
squashed with main commit.
Signed-off-by: Krzysztof Kozlowski <k.kozlowski at samsung.com>
---
arch/m68k/kernel/dma.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/m68k/kernel/dma.c b/arch/m68k/kernel/dma.c
index cbc78b4117b5..8cf97cbadc91 100644
--- a/arch/m68k/kernel/dma.c
+++
2020 Nov 03
0
[RFC] Backend for Motorola 6800 series CPU (M68k)
Hi Min!
On 11/3/20 6:10 PM, Min-Yih Hsu wrote:
> Showing the prerequisites to become an experimental target and eventually,
> an official target. We're currently struggling on setting up the buildbot
> but I believe Adrian (CC-ed) is working on that. So I hope the patches can
> be sorted out while waiting for the buildbot.
The m68k machine is actually already up and running, I
2020 Nov 13
0
[RFC] Backend for Motorola 6800 series CPU (M68k)
Hello!
On 11/3/20 6:10 PM, Min-Yih Hsu wrote:
> Just a quick update on the Motorola 6800 backend: Based on the feedback,
> "M68k" (with lowercase "k") will now be the canonical target name and
> "m68k" be the target triple name. I've updated all the patches under review
> to reflect this change.
Are there any news on this? The M68k buildbot is ready
2020 Nov 15
0
[RFC] Backend for Motorola 6800 series CPU (M68k)
On 11/15/20 9:33 PM, Simon Pilgrim via llvm-dev wrote:
> As well as the actual patch reviews, has there been official approval that the
> M68k experimental backend can be added to trunk? I guess we need a
> "Backend: M68k" bugzilla component - is there anything else?
Sounds good. I'll file that bug tomorrow.
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
:
2020 Nov 16
0
[RFC] Backend for Motorola 6800 series CPU (M68k)
Hi,
To add to what Renato said:
On 15/11/2020 21:59, Fāng-ruì Sòng via llvm-dev wrote:
> I've looked at a few newer backends in LLVM and I think the policy is
> unclear about how an experimental target is approved and reviewed.
It's generally good form to tag anyone who commented in the mailing list
threads on any patches, especially people who objected. If they're
happy in