Hi All,
HLA v2.6 for FreeBSD is now available from the HLA download site on Webster:
http://homepage.mac.com/randyhyde/webster.cs.ucr.edu/HighLevelAsm/dnld.html
v2.6 includes full PE/COFF native code generation for Win32, ELF native code
generation for Linux and FreeBSD, and Mach-O native code
Hi,
I recently made a couple of calls like the following
// currently in /x/y/z
chdir( /x/y );
rmdir( /x/y/z );
When I did at gwd call, it returned /x/y/z along with ENOTDIR.
Is this a known issue?
I'm making low-level (assembly) calls via int 0x80 to do the above (not C
stdlib), though I
This looks like it might be interesting.
Two comments:
1) Is there a FreeBSD port available?
I assume you mean the PORTS distribution format. The answer is no, not yet.
Someday I'll take the time to figure out how to do this (and RPMs or comparable
things under Linux). In the meantime, all
Hi All,
I am pleased to announce that HLA v1.100 and the HLA standard library (v3.0)
are now running natively under FreeBSD. For those who are unfamiliar with the
product, HLA is a High Level Assembler for the 80x86. It allows you to write
portable 80x86 code that runs under Windows, Linux,
Hello Randy,
First, let me out myself as a fan of yours. It was your book that got me
started on ASM and taught me a lot about computers and logic, plus it
provided some entertainment and mental sustenance in pretty boring
times, so thanks!
Now, as for your problem: I think I have to
Hi All,
Well, I've done some sleuthing and discovered some issues.
First, the dd command produced approximately the same results everyone
else was getting. So I rewrote a version of my test code in C using the
stdlib read call and it had really great performance. Not understanding
why C's code
You should also carefully do an strace or similar on
Windows and Linux as well. You may find that you're
doing a system call per byte on FreeBSD but not on
those other systems.
Certainly this might be possible under Windows, as I have no idea what
happens once I link in one of the various
Hi All,
I recently ported my HLA (High Level Assembler) compiler to FreeBSD and,
along with it, the HLA Standard Library. I have a performance-related
question concerning file I/O.
It appears that character-at-a-time file I/O is *exceptionally* slow. Yes, I
realize that when processing large
-Original Message-
From: Steve Kargl [EMAIL PROTECTED]
Sent: Jul 4, 2006 11:40 AM
To: Randall Hyde [EMAIL PROTECTED]
Cc: freebsd-hackers@freebsd.org
Subject: Re: getc in BSD (was FLEX issues)
On Mon, Jul 03, 2006 at 11:34:41AM -0700, Randall Hyde wrote:
The error reported is syntax
Well, having a little bit of time to play around with the issues I'm having
with Flex under GCC, I've determined that the problem occurs in the
following code fragment:
for
(
n = 0;
n num_to_read
(
c =
getcError occurs on this line
(
yyin
)
)
- Original Message -
From: Peter Jeremy [EMAIL PROTECTED]
To: Randall Hyde [EMAIL PROTECTED]
Sent: Saturday, July 01, 2006 11:10 PM
Subject: Re: FLEX, was Re: Return value of malloc(0)
The following compiles without error:
%{
typedef int YYSTYPE;
typedef int YYLTYPE;
/*
** Allow
-Original Message-
How about feeding the C source through the preprocessor, stripping out
the #line directives, compiling it and posting the exact gcc error and
source context.
Okay, I'll try that when I get home. But I was kind of under the impression
that *GCC* runs the preprocessor
-Original Message-
From: Thomas David Rivers [EMAIL PROTECTED]
Sent: Jun 29, 2006 3:17 AM
To: freebsd-hackers@freebsd.org, [EMAIL PROTECTED]
Subject: Re: FLEX, was Re: Return value of malloc(0)
Randall Hyde [EMAIL PROTECTED]
BTW, if anyone is intrested in the full FLEX source, it's
Hi All,
I'm trying to port my compiler from Linux to freeBSD. It looked like a
simple job up to the point I ran my flex code through FLEX on freeBSD. When
GCC processes lex.yy.c I get a complaint about an illegal numeric constant
in yy_get_next_buffer, which is all FLEX generated (or prewritten)
Without seeing the code or the actual error message, I'm
guessing the answer is 42. Perhaps, some detail might
be appropriate.
I seriously doubt seeing the code will do much good.
Here's the offending line:
YY_INPUT( (yy_current_buffer-yy_ch_buf[number_to_move]),
yy_n_chars,
15 matches
Mail list logo