This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libstdc++: actually use BUFSIZE for basic_filebufs


Hi again,
> Florian Weimer wrote:
>   
>> The actual buffer is heap-allocated, so this shouldn't be an issue.
>> Inter-procedural constant propagation could be a problem, but I doubt
>> GCC is smart enough for that (and the semantics will need to be
>> carefully chosen for templatized code anyway).
>>   
>>     
> Oh yes, dumb me, I was also noticing the same.
>   
Let's see if we have some encouraging numbers, but I'm still a little
nervous about this change. What happens if we link together two .o and
one has the old version of the constructor inlined, the other uses the
new version as exported by the *.so?

Paolo.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]