public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rony Paul <ronypaul77@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: compilation error
Date: Wed, 08 Jun 2011 12:25:00 -0000	[thread overview]
Message-ID: <BANLkTi=eSxkE3qCdFZf42pEZHYy0npLE4w@mail.gmail.com> (raw)

Dear All,

could you please tell me what type of error is the following code returning?

make[5]: Entering directory `/home/kosarker/Work/build-gcc/gcc'
/home/kosarker/Work/build-gcc/./gcc/xgcc
-B/home/kosarker/Work/build-gcc/./gcc/ -B/usr/local/spu/bin/
-B/usr/local/spu/lib/ -isystem /usr/local/spu/include -isystem
/usr/local/spu/sys-include    -O2 -g -O2 -DIN_GCC
-DCROSS_DIRECTORY_STRUCTURE  -W -Wall -Wwrite-strings -Wcast-qual
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-isystem ./include  -I.
-I/home/kosarker/Work/build-gcc/spu/mea64/libgcc -I../../gcc-4.5.0/gcc
-I../../gcc-4.5.0/gcc//home/kosarker/Work/build-gcc/spu/mea64/libgcc
-I../../gcc-4.5.0/gcc/../include
-I../../gcc-4.5.0/gcc/../libcpp/include
-I../../gcc-4.5.0/gcc/../libdecnumber
-I../../gcc-4.5.0/gcc/../libdecnumber/dpd -I../libdecnumber    -g -O2
-mea64 -g0 -finhibit-size-directive -fno-inline -fno-exceptions
-fno-zero-initialized-in-bss -fno-toplevel-reorder -fno-tree-vectorize
-Dinhibit_libc  \
	  -c ../../gcc-4.5.0/gcc/crtstuff.c -DCRT_BEGIN \
	  -o /home/kosarker/Work/build-gcc/spu/mea64/libgcc/crtbegin.o
../../gcc-4.5.0/gcc/crtstuff.c:249:1: internal compiler error:
Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[5]: *** [/home/kosarker/Work/build-gcc/spu/mea64/libgcc/crtbegin.o] Error 1
make[5]: Leaving directory `/home/kosarker/Work/build-gcc/gcc'
make[4]: *** [gcc-extra-parts] Error 2
make[4]: Leaving directory `/home/kosarker/Work/build-gcc/spu/mea64/libgcc'
make[3]: *** [multi-do] Error 1
make[3]: Leaving directory `/home/kosarker/Work/build-gcc/spu/libgcc'
make[2]: *** [all-multi] Error 2
make[2]: Leaving directory `/home/kosarker/Work/build-gcc/spu/libgcc'
make[1]: *** [all-target-libgcc] Error 2
make[1]: Leaving directory `/home/kosarker/Work/build-gcc'
make: *** [all] Error 2


----------------------------------------------------------------------------------------------------------------------------------------------
what I did that in the file c-typeck.c I have added some code, like following :

previously it was :

else if (codel == POINTER_TYPE && coder == INTEGER_TYPE)
    {
      /* An explicit constant 0 can convert to a pointer,
	 or one that results from arithmetic, even including
	 a cast to integer type.  */
	
		WARN_FOR_ASSIGNMENT (location, 0,
			     G_("passing argument %d of %qE makes "
				"pointer from integer without a cast"),
			     G_("assignment makes pointer from integer "
				"without a cast//// konica diff address space"),
			     G_("initialization makes pointer from "
				"integer without a cast"),
			     G_("return makes pointer from integer "
				"without a cast"));
			
		}



I have replaced it with :


else if (codel == POINTER_TYPE && coder == INTEGER_TYPE)
    {
      /* An explicit constant 0 can convert to a pointer,
	 or one that results from arithmetic, even including
	 a cast to integer type.  */

             tree ttl = TREE_TYPE (type);
	      tree ttr = TREE_TYPE (rhstype);
	      tree mvl = ttl;
	      tree mvr = ttr;
	      bool is_opaque_pointer;
	      int target_cmp = 0;   /* Cache comp_target_types () result.  */
	      addr_space_t asl;
	      addr_space_t asr;

   	      asl = TYPE_ADDR_SPACE (ttl);
	      asr = TYPE_ADDR_SPACE (ttr);

		if (asr != asl )
		{
		
		    WARN_FOR_ASSIGNMENT (location, 0,
			     G_("passing argument %d of %qE makes "
				"pointer from integer without a cast"),
			     G_("assignment makes pointer from integer "
				"without a cast"),
			     G_("initialization makes pointer from "
				"integer without a cast"),
			     G_("return makes pointer from integer "
				"without a cast"));
			
		}

             reply	other threads:[~2011-06-08 11:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 12:25 Rony Paul [this message]
2011-06-08 13:31 ` Jonathan Wakely
2011-06-08 13:47 ` Ian Lance Taylor
  -- strict thread matches above, loose matches on Subject: below --
2012-08-15 15:43 Configuration Error Jonathan Wakely
2012-08-15 17:49 ` B B
2012-08-15 17:57   ` Jonathan Wakely
2012-08-15 18:03     ` Compilation Error Ron Stubbs
2012-08-15 18:14       ` Marc Glisse
2012-08-15 18:46       ` B B
     [not found]         ` <CAH6eHdRV5NLCO-+iJw1FHqw+6EV-LSCNkhF-SJ0jZUPtdbwFKQ@mail.gmail.com>
2012-08-15 19:25           ` Jonathan Wakely
2012-08-15 19:36     ` Ron Stubbs
2012-08-16  3:59       ` Marc Glisse
2012-08-16 13:29         ` Ron Stubbs
2012-08-16 15:15           ` Tim Prince
2012-08-16 20:06           ` Marc Glisse
2012-08-17  0:12             ` Ron Stubbs
2012-08-17  7:23               ` Marc Glisse
2012-08-17  8:23                 ` Jonathan Wakely
2006-10-07 18:58 compilation error ranjith kumar
2006-10-07 19:36 ` Tim Prince
2005-07-18  4:24 Compilation error Oleg Kotsyurbiy
2005-07-18  5:51 ` Ian Lance Taylor
2005-07-18  7:45   ` Arturas Moskvinas
2000-02-21 10:27 Jose Miguel A.C.Pires
2000-02-21 10:39 ` llewelly
2000-04-01  0:00   ` llewelly
2000-04-01  0:00 ` Jose Miguel A.C.Pires

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='BANLkTi=eSxkE3qCdFZf42pEZHYy0npLE4w@mail.gmail.com' \
    --to=ronypaul77@gmail.com \
    --cc=gcc-help@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).