I'm going to appologize up front for posting frequently, but I'm still crawling up the learning curve. (*)

I'm creating a precompiled header and I'm getting the following output:

Internal error: ph 1114
-- errorlevel 1

Clearly I've uncovered a compiler "feature" (**). The question is what's the workaround [the obvious one being to not use precompiled headers] and how soon can this feature get fixed?


-scooter

(*) I've resorted to XEmacs and smake instead of the IDDE.
(**) There are no bugs, only undiscovered features.

"Scott Michel" <scottm@cs.ucla.edu> wrote in message news:bucs0g$173i$1@digitaldaemon.com...
> I'm creating a precompiled header and I'm getting the following output:
>
> Internal error: ph 1114
> -- errorlevel 1
>
> Clearly I've uncovered a compiler "feature" (**). The question is what's
the
> workaround [the obvious one being to not use precompiled headers] and how soon can this feature get fixed?

I need to be able to reproduce it to fix it. See www.digitalmars.com/faq.html#error

Walter wrote:
> "Scott Michel" <scottm@cs.ucla.edu> wrote in message news:bucs0g$173i$1@digitaldaemon.com...
>> I'm creating a precompiled header and I'm getting the following output:
>>
>> Internal error: ph 1114
>> -- errorlevel 1
>>
>> Clearly I've uncovered a compiler "feature" (**). The question is what's
> the
>> workaround [the obvious one being to not use precompiled headers] and how soon can this feature get fixed?

Pardon my presumptuousness. No gauruntees that it will get fixed...

> I need to be able to reproduce it to fix it. See www.digitalmars.com/faq.html#error

I've tried '-e -llisting.lst', but the output appears to get truncated (buffer not flushed when assert is triggered?) I'll test to see if the error is reproducable on just that fragment that gets output and send the fragment if it is reproducable. Otherwise, I'll have to spend time to narrow the problem down to its minimum, which might not be 10 lines or less.


-scooter

Walter wrote:
> "Scott Michel" <scottm@cs.ucla.edu> wrote in message news:bucs0g$173i$1@digitaldaemon.com...
>> I'm creating a precompiled header and I'm getting the following output:
>>
>> Internal error: ph 1114
>> -- errorlevel 1
>>
>> Clearly I've uncovered a compiler "feature" (**). The question is what's
> the
>> workaround [the obvious one being to not use precompiled headers] and how soon can this feature get fixed?
> 
> I need to be able to reproduce it to fix it. See www.digitalmars.com/faq.html#error

Much easier than I thought, it's a one line header file:

   --- brokenHeader.h ---
   #include <iostream>
   --- brokenHeader.h ---

I'm compiling it as follows:

   sc -cpp -I\dm\stlport\stlport -HFbrokenHeader.sym brokenHeader.h

Produces:

   Internal error: ph 1114
   -- errorlevel 1

I did some header file chasing and was able to narrow the internal error down to the include <stl/_algobase.c>. I wasn't able to narrow the bug to any specific line in _algobase.c.


-scooter

Scott Michel wrote:
> Walter wrote:
>> "Scott Michel" <scottm@cs.ucla.edu> wrote in message news:bucs0g$173i$1@digitaldaemon.com...
>>> I'm creating a precompiled header and I'm getting the following output:
>>>
>>> Internal error: ph 1114
>>> -- errorlevel 1
>>>
>>> Clearly I've uncovered a compiler "feature" (**). The question is what's
>> the
>>> workaround [the obvious one being to not use precompiled headers] and how soon can this feature get fixed?
>> 
>> I need to be able to reproduce it to fix it. See www.digitalmars.com/faq.html#error
> 
> Much easier than I thought, it's a one line header file:
> 
>    --- brokenHeader.h ---
>    #include <iostream>
>    --- brokenHeader.h ---
> 
> I'm compiling it as follows:
> 
>    sc -cpp -I\dm\stlport\stlport -HFbrokenHeader.sym brokenHeader.h
> 
> Produces:
> 
>    Internal error: ph 1114
>    -- errorlevel 1

Taking a break from dissertation writing, I've tracked the problem down a little more to stl/_iterator.h. If you try to compile _iterator.h by itself, everything is fine. When used in _algobase.c, however, the following lines 118-128 are the problem:

template <class _Iterator>
inline bool  _STLP_CALL operator==(const reverse_iterator<_Iterator>& __x,
                       const reverse_iterator<_Iterator>& __y) {
  return __x.base() == __y.base();
}

template <class _Iterator>
inline bool _STLP_CALL operator<(const reverse_iterator<_Iterator>& __x,
                      const reverse_iterator<_Iterator>& __y) {
  return __y.base() < __x.base();
}

If these lines are #if 0'd out, then the ph.c 1114 assert doesn't get triggered.


-scooter

Scott Michel wrote:
> I did some header file chasing and was able to narrow the internal error
> down to the include <stl/_algobase.c>. I wasn't able to narrow the bug to
> any specific line in _algobase.c.
> 
> 
> -scooter
> 
> Scott Michel wrote:
> 
>>Walter wrote:
>>
>>>"Scott Michel" <scottm@cs.ucla.edu> wrote in message
>>>news:bucs0g$173i$1@digitaldaemon.com...
>>>
>>>>I'm creating a precompiled header and I'm getting the following output:
>>>>
>>>>Internal error: ph 1114
>>>>-- errorlevel 1
>>>>
>>>>Clearly I've uncovered a compiler "feature" (**). The question is what's
>>>
>>>the
>>>
>>>>workaround [the obvious one being to not use precompiled headers] and
>>>>how soon can this feature get fixed?
>>>
>>>I need to be able to reproduce it to fix it. See
>>>www.digitalmars.com/faq.html#error
>>
>>Much easier than I thought, it's a one line header file:
>>
>>   --- brokenHeader.h ---
>>   #include <iostream>
>>   --- brokenHeader.h ---
>>
>>I'm compiling it as follows:
>>
>>   sc -cpp -I\dm\stlport\stlport -HFbrokenHeader.sym brokenHeader.h
>>
>>Produces:
>>
>>   Internal error: ph 1114
>>   -- errorlevel 1
> 
> 

"Scott Michel" <scottm@cs.ucla.edu> wrote in message news:bud3l7$1j7p$1@digitaldaemon.com...
> Much easier than I thought, it's a one line header file:
>
>    --- brokenHeader.h ---
>    #include <iostream>
>    --- brokenHeader.h ---
>
> I'm compiling it as follows:
>
>    sc -cpp -I\dm\stlport\stlport -HFbrokenHeader.sym brokenHeader.h
>
> Produces:
>
>    Internal error: ph 1114
>    -- errorlevel 1

Thanks. That's just what I need. -Walter

Yes this problem has had me going for a while too. In fact it only seems to be the first operator, the equality operator, that causes the 1114 internal error for me.

I'd love to know when this is fixed as I have a large VC++ project that uses precompiled headers all the way through and having to compile these everytime would really slow things down.

Thanks.

Regards,
Phil


-scooter- wrote:

> Taking a break from dissertation writing, I've tracked the problem down a little more to stl/_iterator.h. If you try to compile _iterator.h by itself, everything is fine. When used in _algobase.c, however, the following lines 118-128 are the problem:
> 
> template <class _Iterator>
> inline bool  _STLP_CALL operator==(const reverse_iterator<_Iterator>& __x,
>                        const reverse_iterator<_Iterator>& __y) {
>   return __x.base() == __y.base();
> }
> 
> template <class _Iterator>
> inline bool _STLP_CALL operator<(const reverse_iterator<_Iterator>& __x,
>                       const reverse_iterator<_Iterator>& __y) {
>   return __y.base() < __x.base();
> }
> 
> If these lines are #if 0'd out, then the ph.c 1114 assert doesn't get triggered.
> 
> 
> -scooter
> 
> Scott Michel wrote:
> 
>> I did some header file chasing and was able to narrow the internal error
>> down to the include <stl/_algobase.c>. I wasn't able to narrow the bug to
>> any specific line in _algobase.c.
>>
>>
>> -scooter
>>
>> Scott Michel wrote:
>>
>>> Walter wrote:
>>>
>>>> "Scott Michel" <scottm@cs.ucla.edu> wrote in message
>>>> news:bucs0g$173i$1@digitaldaemon.com...
>>>>
>>>>> I'm creating a precompiled header and I'm getting the following output:
>>>>>
>>>>> Internal error: ph 1114
>>>>> -- errorlevel 1
>>>>>
>>>>> Clearly I've uncovered a compiler "feature" (**). The question is what's
>>>>
>>>>
>>>> the
>>>>
>>>>> workaround [the obvious one being to not use precompiled headers] and
>>>>> how soon can this feature get fixed?
>>>>
>>>>
>>>> I need to be able to reproduce it to fix it. See
>>>> www.digitalmars.com/faq.html#error
>>>
>>>
>>> Much easier than I thought, it's a one line header file:
>>>
>>>   --- brokenHeader.h ---
>>>   #include <iostream>
>>>   --- brokenHeader.h ---
>>>
>>> I'm compiling it as follows:
>>>
>>>   sc -cpp -I\dm\stlport\stlport -HFbrokenHeader.sym brokenHeader.h
>>>
>>> Produces:
>>>
>>>   Internal error: ph 1114
>>>   -- errorlevel 1
>>
>>
>>
> 

can someone help fixing this and explain its meaning a little:

Internal error: cod1 1280

thank you

Benoit

"trembb22" <trembb22_member@pathlink.com> wrote in message news:coibes$21rv$1@digitaldaemon.com...
> can someone help fixing this and explain its meaning a little:
>
> Internal error: cod1 1280

This should help: www.digitalmars.com/bugs.html