public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "m mariga" <ma_ariga@yahoo.co.jp>
To: "John Dallaway" <john@dallaway.org.uk>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: h8300 cannot find libgcc.a
Date: Thu, 23 Jul 2009 21:32:00 -0000	[thread overview]
Message-ID: <407D126036C3460AB7AA0264475F04E0@masahiro> (raw)
In-Reply-To: <4A671AEE.2000101@dallaway.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]

Hello,John,and everybody,

I studied GCC3.3.2 patch and really applied to GCC3.3.2 source.
When I compared differences and tried to convert GCC4.4.0 source,there 
appeared one difficult problem.
Would you please teach me ?
I append before-patch source after-patch source and gcc4.4.0 source in 
compressed form.

The patch changes next four files.
/gcc-3.3.2/gcc/config/h8300/extfloatlib.c
/gcc-3.3.2/gcc/config/h8300/float-h8300.h
/gcc-3.3.2/gcc/config/h8300/h8300.h
/gcc-3.3.2/gcc/config/h8300/t-h8300

First two files(extfloatlib.c,float-h8300.h) are newly made,so I think I 
could use them per ce into GCC4.4.0 source.
h8300.h and t-h8300 are modified and I must apply differences to GCC4.4.0 
source.

The patch adds next line into 143 line of GCC3.3.2's h8300.h.

#define TARGET_MODE (target_flags & 16384)

As I tried to insert above define sentence in GCC4.4.0's h8300.h I was 
shocked to have found that there is no TARGET_MODE or target_flags.
Please teach me whether it is alright that I omit to insert above define 
sentence at all.
Or if it is necessary to add it,could you teach me how to do it ?
I am very obliged.

And about another differences I intend to add the same sentences int 
GCC4.4.0's h8300.h and t-h8300.
If you notice carelessness could you enlighten me.

I am sorry to bother you but you are my only rescue.

m mariga

[-- Attachment #2: sources.tar.bz2 --]
[-- Type: application/octet-stream, Size: 29099 bytes --]

[-- Attachment #3: Type: text/plain, Size: 148 bytes --]

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2009-07-23 21:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 14:08 [ECOS] " m mariga
2009-07-21 15:04 ` [ECOS] " John Dallaway
2009-07-22 12:28   ` m mariga
2009-07-22 13:58     ` John Dallaway
2009-07-23 21:32       ` m mariga [this message]
2009-07-24  8:34         ` John Dallaway
2009-07-28 14:40           ` m mariga
2009-08-09 23:11             ` m mariga
2009-08-17  7:42               ` John Dallaway
2009-09-04  5:54               ` [ECOS] How to set GDB Stub Options in order to run insight ? m mariga
2009-09-04  9:38                 ` [ECOS] " John Dallaway
2009-09-04 18:33                   ` m mariga
2009-09-07  9:40                     ` m mariga
2009-09-07 11:31                       ` John Dallaway
2009-09-07 16:10                         ` [ECOS] cyg_scheduler_lock and DSR's Jim Bradleigh
2009-09-11 20:37                           ` Bart Veer
2009-09-08 10:15                         ` [ECOS] Re: How to set GDB Stub Options in order to run insight ? m mariga
2009-09-28  9:54                           ` [ECOS] About h8000 eCos GDB-Stub m mariga
2009-09-30 10:06                             ` m mariga
2009-10-16 14:34                               ` [ECOS] How to connect RedBoot via Telnet running application m mariga
2009-10-16 14:42                                 ` Gary Thomas
     [not found]                                   ` <6FC88324D6C144EFB39FFE3CBF0E5B8D@masahiro>
2009-10-16 15:40                                     ` Gary Thomas
2009-10-16 16:11                                       ` m mariga
2009-10-16 16:43                                       ` m mariga
2009-10-16 16:54                                         ` Gary Thomas
2009-09-19  1:51                         ` [ECOS] Re: How to set GDB Stub Options in order to run insight ? m mariga

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=407D126036C3460AB7AA0264475F04E0@masahiro \
    --to=ma_ariga@yahoo.co.jp \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=john@dallaway.org.uk \
    /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).