Re: Structure alignment with GCC

Re: Structure alignment with GCC

[Michael Sokolov]

David A. Desrosiers <hacker@downcity.net> wrote:

> Hey, we're not *ALL* bad. 

That was directed at the PalmOS designers (the assembly-phobiac C fans who
couldn't grasp the notion of an ABI), not the poor people who develop *for*
PalmOS and have to deal with that morass, which is more of a sandbox run over
by a truck.

> [...] but it's still arrving to
> users as a series of patches against gcc. The saving grace is that the
> patches apply "mostly" cleanly. A little hand-coaxing of them into place
> is almost always required.

Hmm, I can't see how the patches in the prc-tools-0.6.0beta tarball can fail to
apply cleanly against binutils-2.9.1, gcc-2.95.2, and gdb-4.18, as they are
direct diff -urN's against those GNU dists.

But this is not where the real problem with these patches is. PalmOS should be
just a regular target, nothing more, nothing less. The Cygnus/GNU toolchain can
target everything from the tiniest embedded MCUs, probably even some usable for
bionic implants (Alexandre and others working on the MN10200 and MN10300 ports,
do these have anything to do with the MN1068-06 that Agent Scully has in the
back of her neck in the X-Files? :-), to the largest supermainframes.
Everything in between included. The same design philosophy and paradigm works
for all targets. For the people at Palm to think that their wonderful OS needs
its own toolchain with their own quite different world view is a little
megalomaniac. PalmOS should be a regular target, and the way the toolchain is
built, what belongs in the toolchain and what belongs elsewhere, etc. should
all be exactly the same as for any other target (it is the same for all
existing targets). This does not hold for PRC-Tools and the patches used there.

> Ideally a -palmos build target would be nice, but
> we're not there yet.

Actually, it will be called m68k-ipgpe or something like that. ipgpe and not
palmos, because I cannot speak for PalmOS at large, only for my environment for
it, IPGPE. We are not targeting raw PalmOS without any environments, we are
targeting the IPGPE environment with its rules as to data access, etc. As my
disagreement with John Marshall shows very well, there can and will be many
different environments for PalmOS. Now someone could theoretically make a
target for raw PalmOS without any environment, but given its extremely little
usefulness, I doubt that anyone will ever do it. About all you can write for
truly raw PalmOS without an environment is a bare code resource without any
data. Any global data, any application startup code, or anything that goes
beyond one code resource requires an environment, and as the real life has
already shown, people will always disagree on the design of these environments
and write many competing different ones.

--
Michael Sokolov		Harhan Engineering Laboratory
Public Service Agent	International Free Computing Task Force
			International Engineering and Science Task Force
			615 N GOOD LATIMER EXPY STE #4
			DALLAS TX 75204-5852 USA

Phone: +1-214-824-7693 (Harhan Eng Lab office)
E-mail: msokolov@ivan.Harhan.ORG (ARPA TCP/SMTP) (UUCP coming soon)

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Long Long Support for m68K targets

[David Williams]

Hi All,

I want to be able to use printf with support for 64 bit integers. I am compiling
GCC 2.95.2 with newlib 1.8.2 under a cygwin 1.1.4 environment. The code seems to be
there in vfprintf.c, however it does not seem to be enabled when the library is
compiled. It relies on a macro variable WANT_PRINTF_LONG_LONG being defined. My
question is where or how should I define this variable. Searching through the
configure files I found some lines that suggest if the host defined is cygwin then
this variable will be defined. My host is cygwin however the code either doesnt
work or wasnt enabled when I tried to use it.

My script skills are practically non-existant (guessing mostly) so I would
apreciate some help on this one. There does not seem to be an easy way to approach
the configure/make system - its huge and complex - at least from where I am
starting!

TIA
Dave



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: Long Long Support for m68K targets

[Michael Sokolov]

"Russ.Shaw" <russell@webaxs.net> wrote:

> When i install newlib-1.8.2, gcc, and binutils on a pc linux
> system, where should configure.texi and porting.texi get installed?

Nowhere. .texi files are not installed, they stay in the source tree. If you
have texinfo, you can do a make info to make .info files from them, which you
can then install with make install-info. But as I've said, I personally don't
do this because I prefer to read them directly with vi in the source tree. But
then of course I'm different from most other people. :-) I'm a regular
Cygnus/GNU toolchain developer and spend most of my time in the source tree, so
it's more convenient for me to read all the docs right there. But of course, I
don't expect this from others. :-)

--
Michael Sokolov		Harhan Engineering Laboratory
Public Service Agent	International Free Computing Task Force
			International Engineering and Science Task Force
			615 N GOOD LATIMER EXPY STE #4
			DALLAS TX 75204-5852 USA

Phone: +1-214-824-7693 (Harhan Eng Lab office)
E-mail: msokolov@ivan.Harhan.ORG (ARPA TCP/SMTP) (UUCP coming soon)

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: Long Long Support for m68K targets

[Russ.Shaw]

When i install newlib-1.8.2, gcc, and binutils on a pc linux
system, where should configure.texi and porting.texi get installed?

Michael Sokolov wrote:
> 
> David Williams <davidwilliams@ozemail.com.au> wrote:
> 
> > Thanks for the pointer. Only two problems - where is configure.texi and how do I read
> > it.
> 
> configure.texi is in the etc directory of the Cygnus tree. It should be present
> in all recent GCC/Binutils/GDB releases and other tarballs put up for download
> on sourceware mirrors.
> 
> Officially one is supposed to run .texi files through texinfo, but I personally
> prefer to read them directly in a file viewer (that's vi for me personally).
> 
> If you are uncomfortable with this, Ian Lance Taylor, the author of
> configure.texi, has a WWW version of it on his page:
> 
> http://www.airs.com/ian/
> 
-- 
*******************************************
*   Russell Shaw, B.Eng, M.Eng(Research)  *
*      email: russell@webaxs.net          *
*      Victoria, Australia                *
*******************************************

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: Long Long Support for m68K targets

[Michael Sokolov]

David Williams <davidwilliams@ozemail.com.au> wrote:

> Thanks for the pointer. Only two problems - where is configure.texi and how do I read
> it.

configure.texi is in the etc directory of the Cygnus tree. It should be present
in all recent GCC/Binutils/GDB releases and other tarballs put up for download
on sourceware mirrors.

Officially one is supposed to run .texi files through texinfo, but I personally
prefer to read them directly in a file viewer (that's vi for me personally).

If you are uncomfortable with this, Ian Lance Taylor, the author of
configure.texi, has a WWW version of it on his page:

http://www.airs.com/ian/

I hope this helps.

--
Michael Sokolov		Harhan Engineering Laboratory
Public Service Agent	International Free Computing Task Force
			International Engineering and Science Task Force
			615 N GOOD LATIMER EXPY STE #4
			DALLAS TX 75204-5852 USA

Phone: +1-214-824-7693 (Harhan Eng Lab office)
E-mail: msokolov@ivan.Harhan.ORG (ARPA TCP/SMTP) (UUCP coming soon)

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: Long Long Support for m68K targets

[David Williams]

Thanks for the pointer. Only two problems - where is configure.texi and
how do I read
it. I am running cygwin environment and so not all UNIX tools work there
(although a lot
do). I have been using GCC for a couple of years (pre-built binaries of
course) and I
have used a limited amount of UNIX tools/programs during that time.

Dave.

Michael Sokolov wrote:

> If you haven't already, read configure.texi. I have found it very good.
>

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: Long Long Support for m68K targets

[Michael Sokolov]

David Williams <davidwilliams@ozemail.com.au> wrote:

> My script skills are practically non-existant (guessing mostly) so I would
> apreciate some help on this one. There does not seem to be an easy way to approach
> the configure/make system - its huge and complex - at least from where I am
> starting!

If you haven't already, read configure.texi. I have found it very good.

--
Michael Sokolov		Harhan Engineering Laboratory
Public Service Agent	International Free Computing Task Force
			International Engineering and Science Task Force
			615 N GOOD LATIMER EXPY STE #4
			DALLAS TX 75204-5852 USA

Phone: +1-214-824-7693 (Harhan Eng Lab office)
E-mail: msokolov@ivan.Harhan.ORG (ARPA TCP/SMTP) (UUCP coming soon)

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com