Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

speters (1787)

  (email not shown publicly)
AOL IM: fisharerojo (Add Buddy, Send Message)


Journal of speters (1787)

Monday March 26, 2007
03:15 PM

[Perl 6 Microgrant] First steps

[ #32803 ]

So, now it's official. Time to go to work.

The first thing I want to look at is Intel C++ support for Parrot. I have to take this on somewhat carefully for a few reasons.

  • Like gcc, Intel C++ spans multiple operating systems including Windows and Mac OS X.
  • Compiler flags differ depending on the OS.
  • Most annoyingly, Intel C++ tries to look like gcc, but isn't anywhere near compatible.
  • Advice from Klortho #11912 applies to icc's math capabilities

I need to look Parrot's current processes for identifying Intel C++ so we do not have to repeat the logic for each operating system hint file where Intel C++ is supported. My thoughts now are to identify Intel C++ earlier in the Parrot configuration chain, but I haven't decided yet whether this should be when we check for gcc, or if this check should be done separately.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Just out of curiosity -- why do you want to get those particular platforms working? C++ is puzzling since afaik Parrot is written in C; Sun and Intel is puzzling since gcc is available on Linux.
    • gcc isn't the only compiler...

      This is one of the stated goals:

      Similarly, compiling Parrot with Intel C++ and Sun Studio 12 for Linux, application of any necessary patches, and cleanup of compiler specific issues.
      • I guess I was really asking: _why_ are those the goals? I'm not trying to be snippy here; I simply genuinely don't understand why gcc doesn't suffice. I imagine there's a good reason; I just don't know what it is.
        • While gcc is generally a good all purpose compiler, other compilers are often more strict about writing good C code and typically reward you with better optimization, smaller executables and libraries, or a combination of the two. My experiences with Perl 5 is that both compilers generate smaller and faster Perl execuables than gcc. I would assume that this would be plus for embedded systems developers. Intel C++ is also used by some Gentoo users as their default compiler. Making Parrot work with Intel

          • I do not follow the mailing lists much but isn't a c++ compiler (actually maybe I mean a c++ aware linker) required if you want to use ICU as part of parrot? I do not think there has been much discussion of late but at one stage icu was supposed to be the default way for parrot to handle character sets stuff.
            • A C++ compiler is required for linking, but not for compiling. A C++ compiler trying to compile Parrot would run into problem quickly, but it can handle linking the .o's just fine.

  • I really look forward to your work. This is an excellent grant.

    • Thanks! I sincerely hope I can get things working again for some of the platforms, and better than before for the rest.

  • I saw in the TPF news wossname that "as I only have guest access for the majority of these platforms, the work is dependent on continued access to these systems". I'm happy to set up an account for you on OpenBSD if you need it.
    • Oh, sorry I missed your post. I do have the assorted BSDs hanging around the house. However, I can't quite get a HP Superdome to fit nicely under my desk ;)