From: "Pavel Pisa;research student" <pisa@waltz.felk.cvut.cz>
To: gcc@gcc.gnu.org
Subject: GCC and NT DDK - still problems
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.04.9909130930300.29122-100000@fu.felk.cvut.cz> (raw)
Message-ID: <19990930180200.hB50_FnmbSDGbewhvfA0iW__yfqjS_zqbVhcumWBlv0@z> (raw)
Hello everybody,
I am developing GPLed RS-485 9-bit driver for Linux and NT.
It works OK under both OS, but I like to compile
it by GCC under NT in future.
GCC team helped me some time ago with anonymous
structs and unions. Latest versions of MinGW32 port
of GCC can parse and compile my patched vesions of NTDDK.H
and NTDEF.H. If somebody have interrest I can send diffs.
But I have stuck on "fastcall" calling convention.
It is register calling convention used in VC 6.0
and NT Kernel. It is similar to attrib((regparms(2)))
but uses another order of registers.
GCC : EAX, EDX, ECX
VC : ECX, EDX
I have looked at GCC source, but it seems, that
registers for parameters are used in hardcoded order
based on registers numbering in GCC. I do not like
to change numbering => it leads to many other
problems.
It would be great, if allocation order of registers
used for parameters can be described same way as
allocation order of registers for local parameters.
There is second problem, function names of "fastcall"
functions are decorated such way, that they begin
with "@" instead of "_". GCC doesnot use this.
It makes problems to binutils too.
I have some more points to binutils. They are related
to above, so I hope, that I can add them to GCC list.
I have problems with binutils-2.9x and empty libraries.
It leads to SIGSEGV. 2.8x was OK. Repair is there
binutils-empty-ar-patch
-------------------------------------------------------
--- ldfile.c.orig Sat Jul 10 15:57:03 1999
+++ ldfile.c Fri Aug 6 09:44:02 1999
@@ -143,11 +143,18 @@
else
check = entry->the_bfd;
+ if(! check)
+ {
+ einfo (_("%P: openning empty archive %s when searching for %s\n"),
+ attempt, entry->local_sym_name);
+ return true;
+ }
+
if (! bfd_check_format (check, bfd_object))
return true;
if (bfd_arch_get_compatible (check, output_bfd) == NULL)
{
- einfo (_("%P: skipping incompatible %s when searching for %s"),
+ einfo (_("%P: skipping incompatible %s when searching for %s\n"),
attempt, entry->local_sym_name);
bfd_close (entry->the_bfd);
entry->the_bfd = NULL;
-------------------------------------------------------
I have written program, which is able to parse MS import libraries.
Output is DEF file, but there are problems with "@" in front again.
I can send my source on request.
Best regards and thanks for attention
Pavel Pisa
pisa@cmp.felk.cvut.cz
http://cmp.felk.cvut.cz/~pisa
PS: I will be pleased, if you can CC directly to me
next reply other threads:[~1999-09-30 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 0:40 Pavel Pisa;research student [this message]
1999-09-13 8:52 ` Rask Ingemann Lambertsen
1999-09-30 18:02 ` Rask Ingemann Lambertsen
1999-09-30 18:02 ` Pavel Pisa;research student
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=Pine.LNX.4.04.9909130930300.29122-100000@fu.felk.cvut.cz \
--to=pisa@waltz.felk.cvut.cz \
--cc=gcc@gcc.gnu.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 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).