Re: overlapping strncpy/memcpy errors via valgrind
От | anarazel@anarazel.de |
---|---|
Тема | Re: overlapping strncpy/memcpy errors via valgrind |
Дата | |
Msg-id | da54cd4c-4cb9-46f8-950c-ce6efffbc918@email.android.com обсуждение исходный текст |
Ответ на | Re: overlapping strncpy/memcpy errors via valgrind (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: overlapping strncpy/memcpy errors via valgrind
|
Список | pgsql-hackers |
Tom Lane <tgl@sss.pgh.pa.us> schrieb: >Boszormenyi Zoltan <zb@cybertec.at> writes: >> Then, why isn't memcpy() skipped if the source and dest are the same? >> It would be a micro-optimization but a valid one. > >No, it'd be more like a micro-pessimization, because the test would be >wasted effort in the vast majority of calls. The *only* reason to do >this would be to shut up valgrind, and that seems annoying. > >I wonder if anyone's tried filing a bug against valgrind to say that it >shouldn't complain about this case. You already need a suppression file to use valgrind sensibly, its easy enough to add it there. Perhaps we should add oneto the tree? --- Please excuse brevity and formatting - I am writing this on my mobile phone.
В списке pgsql-hackers по дате отправления: