search for: result_type

...error: for each function it appears in.) cdr_tds.c:326: error: `connection' undeclared (first use in this function) cdr_tds.c:349: error: too few arguments to function `tds_alloc_context' cdr_tds.c:375: warning: implicit declaration of function `tds_free_connect' cdr_tds.c:389: error: `result_type' undeclared (first use in this function) cdr_tds.c:389: error: too many arguments to function `tds_process_simple_query' cdr_tds.c: In function `tds_load_module': cdr_tds.c:429: warning: unused variable `result_type' make[1]: *** [cdr_tds.o] Error 1 make[1]: Leaving directory `/home...

...326: error: (Each undeclared identifier is reported only once cdr_tds.c:326: error: for each function it appears in.) cdr_tds.c:326: error: `connection' undeclared (first use in this function) cdr_tds.c:379: warning: implicit declaration of function `tds_free_connect' cdr_tds.c:393: error: `result_type' undeclared (first use in this function) cdr_tds.c:393: error: too many arguments to function `tds_process_simple_query' cdr_tds.c: In function `tds_load_module': cdr_tds.c:434: warning: unused variable `result_type' make[1]: *** [cdr_tds.o] Error 1 make: *** [cdr] Error 2 Any Ide...

...gt;> attrgroup_id := #<id> >> attribute_list := <attribute> ( <attribute>)* >> attribute := <name> (= <value>)? >> | <attribuge_id> >> >> … >> >> function_def := <attribute_list> <result_type> @<id> ([argument_list]) <attribute_list> >> > So something like this (no references inside of the 'attributes' statement allowed, cf. above)? > > attributes #1 = { noinline, alignstack=4 } > attributes #2 = { "no-sse" } > > define void...

...derstanding that it would be totally undefined if we arrive at `next_step` without result being set? I know one generic approach, which I've started implementing, but I'm not sure it is a good solution. Instead of using results directly I always store in a local variable: result = alloca result_type tmp = invoke func to store_block unwind landing store_block: store tmp, result br defer_block ... next_step: val = load result Here result would just be undefined if we arrive at `next_step` without having gone through `store_block`. It works, but my guess is that I'm hiding some valuab...

...f.html#i_landingpad leaves some questions open: 1. What happens when actual exception type isn't listed in catch or filter clauses? Does it still return the corresponding structure like if it was listed? Or behavior is undefined? 2. What is 'somety'? Shouldn't it maybe say "result_type" instead? In the instructions printed by clang++, somety is { i8*, i32 }. 3. What are the allowed values and types passed to catch clause? I see that practically type is i8* and value is bitcast (i8** @<typeinfo> to i8*). Is this target specific? If yes, documentation should mention...

...= { <attribute_list> } > attrgroup_id := #<id> > attribute_list := <attribute> ( <attribute>)* > attribute := <name> (= <value>)? > | <attribuge_id> > > … > > function_def := <attribute_list> <result_type> @<id> ([argument_list]) <attribute_list> > So something like this (no references inside of the 'attributes' statement allowed, cf. above)? attributes #1 = { noinline, alignstack=4 } attributes #2 = { "no-sse" } define void @foo() #1 #2 { ret void } This s...

...roup := attributes <attrgroup_id> = { <attribute_list> } attrgroup_id := #<id> attribute_list := <attribute> ( <attribute>)* attribute := <name> (= <value>)? | <attribuge_id> … function_def := <attribute_list> <result_type> @<id> ([argument_list]) <attribute_list> > Target-Dependent Attributes in IR > --------------------------------- > > The front-end is responsible for knowing which target-dependent options are > interesting to the target. Target-dependent attributes are specified...

...tds = NULL; tds_free_connect(connection); connection = NULL; goto connect_fail; } tds_free_connect(connection); connection = NULL; sprintf(query, "USE %s", abcddbname); #ifdef TDS_PRE_0_62 if ((tds_submit_query(tds, query) != TDS_SUCCEED) || (tds_process_simple_query(tds, &result_type) != TDS_SUCCEED || result_type != TDS_CMD_SUCCEED)) { #else if ((tds_submit_query(tds, query) != TDS_SUCCEED) || (tds_process_simple_query(tds) != TDS_SUCCEED)) { #endif ast_log(LOG_ERROR, "Could not change database (%s)\n", abcddbname); goto connect_fail; } connected = 1; return...

...um=9) at util.c:347 #1 0x0045c6d6 in goodread (tds=0xb7938c90, buf=0x2abb220 "?\033F", buflen=8) at net.c:501 #2 0x0045c765 in tds_read_packet (tds=0xb7938c90) at net.c:567 #3 0x004496bf in tds_get_byte (tds=0xb7938c90) at read.c:76 #4 0x0044619f in tds_process_tokens (tds=0xb7938c90, result_type=0x2abb360, done_flags=0x2abb364, flag=26900) at token.c:509 #5 0x00432e7d in odbc_process_tokens (stmt=0xa3f3658, flag=26900) at odbc.c:3268 #6 0x0043736c in _SQLExecute (stmt=0xa3f3658) at odbc.c:3118 #7 0x00439561 in SQLExecDirect (hstmt=0xa3f3658, szSqlStr=0x2abb640 "INSERT INTO cdr...

...to be unwound. Note that you can match a catch clause without being equal to the type in the catch clause (for example because the catch clause type represents some class B, and thus will also match a class A if B derives from A). > 2. What is 'somety'? Shouldn't it maybe say "result_type" instead? In > the instructions printed by clang++, somety is { i8*, i32 }. The type is not specified to allow for exotic exception handling schemes in which returning something funky is useful. The code generators only support Dwarf exception handling and setjmp/longjmp exception handlin...

Hi! This is a proposal to expand the Attributes class to support many different options that will be accessible by all parts of the compiler. Please read and give any feedback you may have. Thanks! -bw Passing Options to Different Parts of the Compiler Problem ======= There is a growing need to pass information from the front-end to different parts of the compiler, especially

...... seems quite clean to me. > attrgroup_id := #<id> > attribute_list := <attribute> ( <attribute>)* > attribute := <name> (= <value>)? > | <attribuge_id> > > … > > function_def := <attribute_list> <result_type> @<id> ([argument_list]) <attribute_list> > > >> Target-Dependent Attributes in IR >> --------------------------------- >> >> The front-end is responsible for knowing which target-dependent options are >> interesting to the target. Target-dependent...

...-1) { /* TODO: Use a macro to write the availability of the query */ if (hq->state != NVC0_HW_QUERY_STATE_READY) @@ -382,6 +393,7 @@ nvc0_hw_get_query_result_resource(struct nvc0_context *nvc0, nvc0->base.push_cb(&nvc0->base, buf, offset, result_type >= PIPE_QUERY_TYPE_I64 ? 2 : 1, ready); + pipe_mutex_unlock(nvc0->screen->base.push_mutex); return; } @@ -469,6 +481,8 @@ nvc0_hw_get_query_result_resource(struct nvc0_context *nvc0, 4 | NVC0_IB_ENTRY_1_NO_PREFETCH);...