search for: last_chr

I did some more optimisation. Most performance hit in Dovecot do "for loop" in string operations. In one case (in message-parser.c) "for loop" has another "for" inside with the same variable used as iterator. This case is very hard to optimise by compiler. I do changes only in top functions listed in oprofile. Maybe I do more in future. Code was analysed and

...3618 (gdb) p ctx->part $3 = (struct message_part *) 0x812e7c0 (gdb) p *ctx $4 = {parser_pool = 0x812b638, part_pool = 0x0, input = 0x8113618, parts = 0x812e730, part = 0x812e7c0, hdr_flags = 3, flags = MESSAGE_PARSER_FLAG_SKIP_BODY_BLOCK, last_boundary = 0x0, boundaries = 0x0, skip = 0, last_chr = 0 '\0', want_count = 0, hdr_parser_ctx = 0x0, parse_next_block = 0x80cc1e0 <preparsed_parse_next_header_init>, part_seen_content_type = 0, broken = 1} (gdb) p *ctx->part $5 = {parent = 0x812e778, next = 0x0, children = 0x0, physical_pos = 688, header_size = {physica...