GSaha567/seq_level_training_data
052
1text,length,is_long_context,metric_val,label_metric2"------------------------------------------------------------------------------3-- --4-- GNAT COMPILER COMPONENTS --5-- --6-- E R R O U T --7-- --8-- S p e c --9-- --10-- Copyright (C) 1992-2020, Free Software Foundation, Inc. --11-- --12-- GNAT is free software; you can redistribute it and/or modify it under --13-- terms of the GNU General Public License as published by the Free Soft- --14-- ware Foundation; either version 3, or (at your option) any later ver- --15-- sion. GNAT is distributed in the hope that it will be useful, but WITH- --16-- OUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY --17-- or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License --18-- for more details. You should have received a copy of the GNU General --19-- Public License distributed with GNAT; see file COPYING3. If not, go to --20-- http://www.gnu.org/licenses for a complete copy of the license. --21-- --22-- GNAT was originally developed by the GNAT team at New York University. --23-- Extensive contributions were provided by Ada Core Technologies Inc. --24-- --25------------------------------------------------------------------------------26 27-- This package contains the routines to output error messages. They are28-- basically system independent, however in some environments, e.g. when the29-- parser is embedded into an editor, it may be appropriate to replace the30-- implementation of this package.31 32with Err_Vars;33with Erroutc;34with Namet; use Namet;35with Table;36with Types; use Types;37with Uintp; use Uintp;38 39with System;40 41package Errout is42 43 Current_Error_Source_File : Source_File_Index44 renames Err_Vars.Current_Error_Source_File;45 -- Id of current messages. Used to post file name when unit changes. This46 -- is initialized to Main_Source_File at the start of a compilation, which47 -- means that no file names will be output unless there are errors in48 -- units other than the main unit. However, if the main unit has a pragma49 -- Source_Reference line, then this is initialized to No_Source_File, to50 -- force an initial reference to the real source file name.51 52 Raise_Exception_On_Error : Nat renames Err_Vars.Raise_Exception_On_Error;53 -- If this value is non-zero, then any attempt to generate an error54 -- message raises the exception Error_Msg_Exception, and the error message55 -- is not output. This is used for defending against junk resulting from56 -- illegalities, and also for substitution of more appropriate error57 -- messages from higher semantic levels. It is a counter so that the58 -- increment/decrement protocol nests neatly.59 60 Error_Msg_Exception : exception renames Err_Vars.Error_Msg_Exception;61 -- Exception raised if Raise_Exception_On_Error is true62 63 Warning_Doc_Switch : Boolean renames Err_Vars.Warning_Doc_Switch;64 -- If this is set True, then the ??/?*?/?$?/?x?/?X? insertion sequences in65 -- error messages generate appropriate tags for the output error messages.66 -- If this switch is False, then these sequences are still recognized (for67 -- the purposes of implementing the pattern matching in pragmas Warnings68 -- (Off,..) and Warning_As_Pragma(...) but do not result in adding the69 -- error message tag. The -gnatw.d switch sets this flag True, -gnatw.D70 -- sets this flag False.71 72 Current_Node : Node_Id := Empty;73 -- Used by Error_Msg as a default Node_Id.74 -- Relevant only when Opt.Include_Subprogram_In_Messages is set.75 76 -----------------------------------77 -- Suppression of Error Messages --78 -----------------------------------79 80 -- In an effort to reduce the impact of redundant error messages, the81 -- error output routines in this package normally suppress certain82 -- classes of messages as follows:83 84 -- 1. Identical messages placed at the same point in the text. Such85 -- duplicate error message result for example from rescanning86 -- sections of the text that contain lexical errors. Only one of87 -- such a set of duplicate messages is output, and the rest are88 -- suppressed.89 90 -- 2. If more than one parser message is generated for a single source91 -- line, then only the first message is output, the remaining92 -- messages on the same line are suppressed.93 94 -- 3. If a message is posted on a node for which a message has been95 -- previously posted, then only the first message is retained. The96 -- Error_Posted flag is used to detect such multiple postings. Note97 -- that this only applies to semantic messages, since otherwise98 -- for parser messages, this would be a special case of case 2.99 100 -- 4. If a message is posted on a node whose Etype or Entity101 -- fields reference entities on which an error message has102 -- already been placed, as indicated by the Error_Posted flag103 -- being set on these entities, then the message is suppressed.104 105 -- 5. If a message attempts to insert an Error node, or a direct106 -- reference to the Any_Type node, then the message is suppressed.107 108 -- 6. Note that cases 2-5 only apply to error messages, not warning109 -- messages. Warning messages are only suppressed for case 1, and110 -- when they come from other than the main extended unit.111 112 -- 7. If an error or warning references an internal name, and we have113 -- already placed an error (not warning) message at that location,114 -- then we assume this is cascaded junk and delete the message.115 116 -- This normal suppression action may be overridden in cases 2-5 (but117 -- not in case 1 or 7) by setting All_Errors mode, or by setting the118 -- unconditional message insertion character (!) as described below.119 120 ---------------------------------------------------------121 -- Error Message Text and Message Insertion Characters --122 ---------------------------------------------------------123 124 -- Error message text strings are composed of lower case letters, digits125 -- and the special characters space, comma, period, colon and semicolon,126 -- apostrophe and parentheses. Special insertion characters can also127 -- appear which cause the error message circuit to modify the given128 -- string as follows:129 130 -- Insertion character % (Percent: insert name from Names table)131 -- The character % is replaced by the text for the name specified by132 -- the Name_Id value stored in Error_Msg_Name_1. A blank precedes the133 -- name if it is preceded by a non-blank character other than left134 -- parenthesis. The name is enclosed in quotes unless manual quotation135 -- mode is set. If the Name_Id is set to No_Name, then no insertion136 -- occurs; if the Name_Id is set to Error_Name, then the string137 -- <error> is inserted. A second and third % may appear in a single138 -- message, similarly replaced by the names which are specified by the139 -- Name_Id values stored in Error_Msg_Name_2 and Error_Msg_Name_3. The140 -- names are decoded and cased according to the current identifier141 -- casing mode. Note: if a unit name ending with %b or %s is passed142 -- for this kind of insertion, this suffix is simply stripped. Use a143 -- unit name insertion ($) to process the suffix.144 --145 -- Note: the special names _xxx (xxx = Pre/Post/Invariant) are changed146 -- to insert the string xxx'Class into the message.147 148 -- Insertion character %% (Double percent: insert literal name)149 -- The character sequence %% acts as described above for %, except150 -- that the name is simply obtained with Get_Name_String and is not151 -- decoded or cased, it is inserted literally from the names table.152 -- A trailing %b or %s is not treated specially.153 --154 -- Note: the special names _xxx (xxx = Pre/Post/Invariant) are changed155 -- to insert the string xxx'Class into the message.156 157 -- Insertion character $ (Dollar: insert unit name from Names table)158 -- The character $ is treated similarly to %, except that the name is159 -- obtained from the Unit_Name_Type value in Error_Msg_Unit_1 and160 -- Error_Msg_Unit_2, as provided by Get_Unit_Name_String in package161 -- Uname. Note that this name includes the postfix (spec) or (body)162 -- strings. If this postfix is not required, use the normal % insertion163 -- for the unit name.164 165 -- Insertion character { (Left brace: insert file name from names table)166 -- The character { is treated similarly to %, except that the input167 -- value is a File_Name_Type value stored in Error_Msg_File_1 or168 -- Error_Msg_File_2 or Error_Msg_File_3. The value is output literally,169 -- enclosed in quotes as for %, but the case is not modified, the170 -- insertion is the exact string stored in the names table without171 -- adjusting the casing.172 173 -- Insertion character * (Asterisk: insert reserved word name)174 -- The insertion character * is treated exactly like % except that the175 -- resulting name is cased according to the default conventions for176 -- reserved words (see package Scans).177 178 -- Insertion character & (Ampersand: insert name from node)179 -- The insertion character & is treated similarly to %, except that180 -- the name is taken from the Chars field of the given node, and may181 -- refer to a child unit name, or a selected component. The casing is,182 -- if possible, taken from the original source reference, which is183 -- obtained from the Sloc field of the given node or nodes. If no Sloc184 -- is available (happens e.g. for nodes in package Standard), then the185 -- default case (see Scans spec) is used. The nodes to be used are186 -- stored in Error_Msg_Node_1, Error_Msg_Node_2. No insertion occurs187 -- for the Empty node, and the Error node results in the insertion of188 -- the characters <error>. In addition, if the special global variable189 -- Error_Msg_Qual_Level is non-zero, then the reference will include190 -- up to the given number of levels of qualification, using the scope191 -- chain.192 --193 -- Note: the special names _xxx (xxx = Pre/Post/Invariant) are changed194 -- to insert the string xxx'Class into the message.195 196 -- Insertion character # (Pound: insert line number reference)197 -- The character # is replaced by the string indicating the source198 -- position stored in Error_Msg_Sloc. There are three cases:199 --200 -- for package Standard: in package Standard201 -- for locations in current file: at line nnn:ccc202 -- for locations in other files: at filename:nnn:ccc203 --204 -- By convention, the # insertion character is only used at the end of205 -- an error message, so the above strings only appear as the last206 -- characters of an error message. The only exceptions to this rule207 -- are that an RM reference may follow in the form (RM .....) and a208 -- right parenthesis may immediately follow the #. In the case of209 -- continued messages, # can only appear at the end of a group of210 -- continuation messages, except that \\\\ messages which always start211 -- a new line end the sequence from the point of view of this rule.212 -- The idea is that for any use of -gnatj, it will still be the case213 -- that a location reference appears only at the end of a line.214 215 -- Note: the output of the string ""at "" is suppressed if the string216 -- "" from"" or "" from "" immediately precedes the insertion character #.217 -- Certain messages read better with from than at.218 219 -- Insertion character } (Right brace: insert type reference)220 -- The character } is replaced by a string describing the type221 -- referenced by the entity whose Id is stored in Error_Msg_Node_1.222 -- The string gives the name or description of the type, and also223 -- where appropriate the location of its declaration. Special cases224 -- like ""some integer type"" are handled appropriately. Only one } is225 -- allowed in a message, since there is not enough room for two (the226 -- insertion can be quite long, including a file name). In addition, if227 -- the special global variable Error_Msg_Qual_Level is non-zero, then228 -- the reference will include up to the given number of levels of229 -- qualification, using the scope chain.230 231 -- Insertion character @ (At: insert column number reference)232 -- The character @ is replaced by null if the RM_Column_Check mode is233 -- off (False). If the switch is on (True), then @ is replaced by the234 -- text string "" in column nnn"" where nnn is the decimal235 -- representation of the column number stored in Error_Msg_Col plus236 -- one (the plus one is because the number is stored 0-origin and237 -- displayed 1-origin).238 239 -- Insertion character ^ (Caret: insert integer value)240 -- The character ^ is replaced by the decimal conversion of the Uint241 -- value stored in Error_Msg_Uint_1, with a possible leading minus.242 -- A second ^ may occur in the message, in which case it is replaced243 -- by the decimal conversion of the Uint value in Error_Msg_Uint_2.244 245 -- Insertion character > (Greater Than: run time name)246 -- The character > is replaced by a string of the form (name) if247 -- Targparm scanned out a Run_Time_Name (see package Targparm for248 -- details). The name is enclosed in parentheses and output in mixed249 -- case mode (upper case after any space in the name). If no run time250 -- name is defined, this insertion character has no effect.251 252 -- Insertion character ! (Exclamation: unconditional message)253 -- The character ! appearing anywhere in the text of a message makes254 -- the message unconditional which means that it is output even if it255 -- would normally be suppressed. See section above for a description256 -- of the cases in which messages are normally suppressed. Note that257 -- in the case of warnings, the meaning is that the warning should not258 -- be removed in dead code (that's the only time that the use of !259 -- has any effect for a warning).260 --261 -- Note: the presence of ! is ignored in continuation messages (i.e.262 -- messages starting with the \\ insertion character). The effect of the263 -- use of ! in a parent message automatically applies to all of its264 -- continuation messages (since we clearly don't want any case in which265 -- continuations are separated from the main message). It is allowable266 -- to put ! in continuation messages, and the usual style is to include267 -- it, since it makes it clear that the continuation is part of an268 -- unconditional message.269 270 -- Insertion character !! (Double exclamation: unconditional warning)271 -- Normally warning messages issued in other than the main unit are272 -- suppressed. If the message contains !! then this suppression is273 -- avoided. This is currently used by the Compile_Time_Warning pragma274 -- to ensure the message for a with'ed unit is output, and for warnings275 -- on ineffective back-end inlining, which is detected in units that276 -- contain subprograms to be inlined in the main program. It is also277 -- used by the Compiler_Unit_Warning pragma for similar reasons.278 279 -- Insertion character ? (Question: warning message)280 -- The character ? appearing anywhere in a message makes the message281 -- warning instead of a normal error message, and the text of the282 -- message will be preceded by ""warning:"" in the normal case. The283 -- handling of warnings if further controlled by the Warning_Mode284 -- option (-w switch), see package Opt for further details, and also by285 -- the current setting from pragma Warnings. This pragma applies only286 -- to warnings issued from the semantic phase (not the parser), but287 -- currently all relevant warnings are posted by the semantic phase288 -- anyway. Messages starting with (style) are also treated as warning289 -- messages.290 --291 -- Note: when a warning message is output, the text of the message is292 -- preceded by ""warning: "" in the normal case. An exception to this293 -- rule occurs when the text of the message starts with ""info: "" in294 -- which case this string is not prepended. This allows callers to295 -- label certain warnings as informational messages, rather than as296 -- warning messages requiring some action.297 --298 -- Note: the presence of ? is ignored in continuation messages (i.e.299 -- messages starting with the \\ insertion character). The warning300 -- status of continuations is determined only by the parent message301 -- which is being continued. It is allowable to put ? in continuation302 -- messages, and the usual style is to include it, since it makes it303 -- clear that the continuation is part of a warning message, but it is304 -- not necessary to go through any computational effort to include it.305 --306 -- Note: this usage is obsolete, use ?? ?*? ?$? ?x? ?X? to specify307 -- the string to be added when Warn_Doc_Switch is set to True. If this308 -- switch is True, then for simple ? messages it has no effect. This309 -- simple form is to ease transition and may be removed later except310 -- for GNATprove-specific messages (info and warnings) which are not311 -- subject to the same GNAT warning switches.312 313 -- Insertion character ?? (Two question marks: default warning)314 -- Like ?, but if the flag Warn_Doc_Switch is True, adds the string315 -- ""[enabled by default]"" at the end of the warning message. For316 -- continuations, use this in each continuation message.317 318 -- Insertion character ?x? (warning with switch)319 -- Like ?, but if the flag Warn_Doc_Switch is True, adds the string320 -- ""[-gnatwx]"" at the end of the warning message. x is a lower case321 -- letter. For continuations, use this on each continuation message.322 323 -- Insertion character ?X? (warning with dot switch)324 -- Like ?, but if the flag Warn_Doc_Switch is True, adds the string325 -- ""[-gnatw.x]"" at the end of the warning message. X is an upper case326 -- letter corresponding to the lower case letter x in the message.327 -- For continuations, use this on each continuation message.328 329 -- Insertion character ?*? (restriction warning)330 -- Like ?, but if the flag Warn_Doc_Switch is True, adds the string331 -- ""[restriction warning]"" at the end of the warning message. For332 -- continuations, use this on each continuation message.333 334 -- Insertion character ?$? (elaboration informational messages)335 -- Like ?, but if the flag Warn_Doc_Switch is True, adds the string336 -- ""[-gnatel]"" at the end of the info message. This is used for the337 -- messages generated by the switch -gnatel. For continuations, use338 -- this on each continuation message.339 340 -- Insertion character < (Less Than: conditional warning message)341 -- The character < appearing anywhere in a message is used for a342 -- conditional error message. If Error_Msg_Warn is True, then the343 -- effect is the same as ? described above, and in particular << <X<344 -- <x< <$< <*< have the effect of ?? ?X? ?x? ?$? ?*? respectively. If345 -- Error_Msg_Warn is False, then the < << or <X< sequence is ignored346 -- and the message is treated as a error rather than a warning.347 348 -- Insertion character A-Z (Upper case letter: Ada reserved word)349 -- If two or more upper case letters appear in the message, they are350 -- taken as an Ada reserved word, and are converted to the default351 -- case for reserved words (see Scans package spec). Surrounding352 -- quotes are added unless manual quotation mode is currently set.353 -- RM and SPARK are special exceptions, they are never treated as354 -- keywords, and just appear verbatim, with no surrounding quotes.355 -- As a special case, 'R'M is used instead of RM (which is not treated356 -- as a keyword) to indicate when the reference to the RM is possibly357 -- not useful anymore, and could possibly be replaced by a comment358 -- in the source.359 360 -- Insertion character ` (Backquote: set manual quotation mode)361 -- The backquote character always appears in pairs. Each backquote of362 -- the pair is replaced by a double quote character. In addition, any363 -- reserved keywords, or name insertions between these backquotes are364 -- not surrounded by the usual automatic double quotes. See the365 -- section below on manual quotation mode for further details.366 367 -- Insertion character ' (Quote: literal character)368 -- Precedes a character which is placed literally into the message.369 -- Used to insert characters into messages that are one of the370 -- insertion characters defined here. Also used for insertion of371 -- upper case letter sequences not to be treated as keywords.372 373 -- Insertion character \\ (Backslash: continuation message)374 -- Indicates that the message is a continuation of a message375 -- previously posted. This is used to ensure that such groups of376 -- messages are treated as a unit. The \\ character must be the first377 -- character of the message text.378 379 -- Insertion character \\\\ (Two backslashes: continuation with new line)380 -- This differs from \\ only in -gnatjnn mode (Error_Message_Line_Length381 -- set non-zero). This sequence forces a new line to start even when382 -- continuations are being gathered into a single message.383 384 -- Insertion character | (Vertical bar: non-serious error)385 -- By default, error messages (other than warning messages) are386 -- considered to be fatal error messages which prevent expansion or387 -- generation of code in the presence of the -gnatQ switch. If the388 -- insertion character | appears, the message is considered to be389 -- non-serious, and does not cause Serious_Errors_Detected to be390 -- incremented (so expansion is not prevented by such a msg). This391 -- insertion character is ignored in continuation messages.392 393 -- Insertion character ~ (Tilde: insert string)394 -- Indicates that Error_Msg_String (1 .. Error_Msg_Strlen) is to be395 -- inserted to replace the ~ character. The string is inserted in the396 -- literal form it appears, without any action on special characters.397 398 -- Insertion character [ (Left bracket: will/would be raised at run time)399 -- This is used in messages about exceptions being raised at run-time.400 -- If the current message is a warning message, then if the code is401 -- executed, the exception will be raised, and [ inserts:402 --403 -- will be raised at run time404 --405 -- If the current message is an error message, then it is an error406 -- because the exception would have been raised and [ inserts:407 --408 -- would have been raised at run time409 --410 -- Typically the message contains a < insertion which means that the411 -- message is a warning or error depending on Error_Msg_Warn. This is412 -- most typically used in the context of messages which are normally413 -- warnings, but are errors in GNATprove mode, corresponding to the414 -- permission in the definition of SPARK that allows an implementation415 -- to reject a program as illegal if a situation arises in which the416 -- compiler can determine that it is certain that a run-time check417 -- would have fail if the statement was executed.418 419 -- Insertion character ] (Right bracket: may/might be raised at run time)420 -- This is like [ except that the insertion messages say may/might,421 -- instead of will/would.422 423 -- Insertion sequence ""(style)"" (style message)424 -- This appears only at the start of the message (and not any of its425 -- continuations, if any), and indicates that the message is a style426 -- message. Style messages are also considered to be warnings, but427 -- they do not get a tag.428 429 -- Insertion sequence ""info: "" (informational message)430 -- This appears only at the start of the message (and not any of its431 -- continuations, if any), and indicates that the message is an info432 -- message. The message will be output with this prefix, and if there433 -- are continuations that are not printed using the -gnatj switch they434 -- will also have this prefix. Informational messages are usually also435 -- warnings, but they don't have to be.436 437 -- Insertion sequence ""low: "" or ""medium: "" or ""high: "" (check message)438 -- This appears only at the start of the message (and not any of its439 -- continuations, if any), and indicates that the message is a check440 -- message. The message will be output with this prefix. Check441 -- messages are not fatal (so are like info messages in that respect)442 -- and are not controlled by pragma Warnings.443 444 -----------------------------------------------------445 -- Global Values Used for Error Message Insertions --446 -----------------------------------------------------447 448 -- The following global variables are essentially additional parameters449 -- passed to the error message routine for insertion sequences described450 -- above. The reason these are passed globally is that the insertion451 -- mechanism is essentially an untyped one in which the appropriate452 -- variables are set depending on the specific insertion characters used.453 454 -- Note that is mandatory that the caller ensure that global variables455 -- are set before the Error_Msg call, otherwise the result is undefined.456 457 -- Also note that calls to Error_Msg and its variants destroy the value of458 -- these global variables, as a way to support the inclusion of multiple459 -- insertion characters of the same type. For example, support for460 -- multiple characters % for a name in the message (up to 3) is461 -- implemented by unconditionally shifting the value for Error_Msg_Nam_2462 -- to Error_Msg_Nam_1 and from Error_Msg_Nam_3 to Error_Msg_Nam_2 after463 -- dealing with insertion character %. The caller should ensure that all464 -- global variables are restored if needed prior to calling Error_Msg.465 466 Error_Msg_Col : Column_Number renames Err_Vars.Error_Msg_Col;467 -- Column for @ insertion character in message468 469 Error_Msg_Uint_1 : Uint renames Err_Vars.Error_Msg_Uint_1;470 Error_Msg_Uint_2 : Uint renames Err_Vars.Error_Msg_Uint_2;471 -- Uint values for ^ insertion characters in message472 473 Error_Msg_Sloc : Source_Ptr renames Err_Vars.Error_Msg_Sloc;474 -- Source location for # insertion character in message475 476 Error_Msg_Name_1 : Name_Id renames Err_Vars.Error_Msg_Name_1;477 Error_Msg_Name_2 : Name_Id renames Err_Vars.Error_Msg_Name_2;478 Error_Msg_Name_3 : Name_Id renames Err_Vars.Error_Msg_Name_3;479 -- Name_Id values for % insertion characters in message480 481 Error_Msg_File_1 : File_Name_Type renames Err_Vars.Error_Msg_File_1;482 Error_Msg_File_2 : File_Name_Type renames Err_Vars.Error_Msg_File_2;483 Error_Msg_File_3 : File_Name_Type renames Err_Vars.Error_Msg_File_3;484 -- File_Name_Type values for { insertion characters in message485 486 Error_Msg_Unit_1 : Unit_Name_Type renames Err_Vars.Error_Msg_Unit_1;487 Error_Msg_Unit_2 : Unit_Name_Type renames Err_Vars.Error_Msg_Unit_2;488 -- Unit_Name_Type values for $ insertion characters in message489 490 Error_Msg_Node_1 : Node_Id renames Err_Vars.Error_Msg_Node_1;491 Error_Msg_Node_2 : Node_Id renames Err_Vars.Error_Msg_Node_2;492 -- Node_Id values for & insertion characters in message493 494 Error_Msg_Qual_Level : Nat renames Err_Vars.Error_Msg_Qual_Level;495 -- Number of levels of qualification required for type name (see the496 -- description of the } insertion character). Note that this value does497 -- not get reset by any Error_Msg call, so the caller is responsible498 -- for resetting it.499 500 Error_Msg_Warn : Boolean renames Err_Vars.Error_Msg_Warn;501 -- Used if current message contains a < insertion character to indicate502 -- if the current message is a warning message. Must be set appropriately503 -- before any call to Error_Msg_xxx with a < insertion character present.504 -- Setting is irrelevant if no < insertion character is present.505 506 Error_Msg_String : String renames Err_Vars.Error_Msg_String;507 Error_Msg_Strlen : Natural renames Err_Vars.Error_Msg_Strlen;508 -- Used if current message contains a ~ insertion character to indicate509 -- insertion of the string Error_Msg_String (1 .. Error_Msg_Strlen).510 511 -----------------------------------------------------512 -- Format of Messages and Manual Quotation Control --513 -----------------------------------------------------514 515 -- Messages are generally all in lower case, except for inserted names516 -- and appear in one of the following three forms:517 518 -- error: text519 -- warning: text520 521 -- The prefixes error and warning are supplied automatically (depending522 -- on the use of the ? insertion character), and the call to the error523 -- message routine supplies the text. The ""error: "" prefix is omitted524 -- in brief error message formats.525 526 -- Reserved Ada keywords in the message are in the default keyword case527 -- (determined from the given source program), surrounded by quotation528 -- marks. This is achieved by spelling the reserved word in upper case529 -- letters, which is recognized as a request for insertion of quotation530 -- marks by the error text processor. Thus for example:531 532 -- Error_Msg_AP (""IS expected"");533 534 -- would result in the output of one of the following:535 536 -- error: ""is"" expected537 -- error: ""IS"" expected538 -- error: ""Is"" expected539 540 -- the choice between these being made by looking at the casing convention541 -- used for keywords (actually the first compilation unit keyword) in the542 -- source file.543 544 -- Note: a special exception is that RM is never treated as a keyword545 -- but instead is copied literally into the message, this avoids the546 -- need for writing 'R'M for all reference manual quotes. A similar547 -- exception is applied to the occurrence of the string SPARK used in548 -- error messages about the SPARK subset of Ada.549 550 -- In the case of names, the default mode for the error text processor551 -- is to surround the name by quotation marks automatically. The case552 -- used for the identifier names is taken from the source program where553 -- possible, and otherwise is the default casing convention taken from554 -- the source file usage.555 556 -- In some cases, better control over the placement of quote marks is557 -- required. This is achieved using manual quotation mode. In this mode,558 -- one or more insertion sequences is surrounded by backquote characters.559 -- The backquote characters are output as double quote marks, and normal560 -- automatic insertion of quotes is suppressed between the double quotes.561 -- For example:562 563 -- Error_Msg_AP (""`END &;` expected"");564 565 -- generates a message like566 567 -- error: ""end Open_Scope;"" expected568 569 -- where the node specifying the name Open_Scope has been stored in570 -- Error_Msg_Node_1 prior to the call. The great majority of error571 -- messages operates in normal quotation mode.572 573 -- Note: the normal automatic insertion of spaces before insertion574 -- sequences (such as those that come from & and %) is suppressed in575 -- manual quotation mode, so blanks, if needed as in the above example,576 -- must be explicitly present.577 578 ----------------------------579 -- Message ID Definitions --580 ----------------------------581 582 subtype Error_Msg_Id is Erroutc.Error_Msg_Id;583 function ""="" (Left, Right : Error_Msg_Id) return Boolean584 renames Erroutc.""="";585 -- A type used to represent specific error messages. Used by the clients586 -- of this package only in the context of the Get_Error_Id and587 -- Change_Error_Text subprograms.588 589 No_Error_Msg : constant Error_Msg_Id := Erroutc.No_Error_Msg;590 -- A constant which is different from any value returned by Get_Error_Id.591 -- Typically used by a client to indicate absense of a saved Id value.592 593 Warning_Msg : Error_Msg_Id := No_Error_Msg;594 -- This is set if a warning message is generated to the ID of the resulting595 -- message. Continuation messages have no effect. It is legitimate for the596 -- client to set this to No_Error_Msg and then test it to see if a warning597 -- message has been issued.598 599 procedure Delete_Warning_And_Continuations (Msg : Error_Msg_Id);600 -- Deletes the given warning message and all its continuations. This is601 -- typically used in conjunction with reading the value of Warning_Msg.602 603 function Get_Msg_Id return Error_Msg_Id renames Erroutc.Get_Msg_Id;604 -- Returns the Id of the message most recently posted using one of the605 -- Error_Msg routines.606 607 function Get_Location (E : Error_Msg_Id) return Source_Ptr608 renames Erroutc.Get_Location;609 -- Returns the flag location of the error message with the given id E610 611 ------------------------612 -- List Pragmas Table --613 ------------------------614 615 -- When a pragma Page or pragma List is encountered by the parser, an616 -- entry is made in the following table. This table is then used to617 -- control the full listing if one is being generated. Note that the618 -- reason we do the processing in the parser is so that we get proper619 -- listing control even in syntax check only mode.620 621 type List_Pragma_Type is (List_On, List_Off, Page);622 623 type List_Pragma_Record is record624 Ptyp : List_Pragma_Type;625 Ploc : Source_Ptr;626 end record;627 628 -- Note: Ploc points to the terminating semicolon in the List_Off and Page629 -- cases, and to the pragma keyword for List_On. In the case of a pragma630 -- List_Off, a List_On entry is also made in the table, pointing to the631 -- pragma keyword. This ensures that, as required, a List (Off) pragma is632 -- listed even in list off mode.633 634 package List_Pragmas is new Table.Table (635 Table_Component_Type => List_Pragma_Record,636 Table_Index_Type => Int,637 Table_Low_Bound => 1,638 Table_Initial => 50,639 Table_Increment => 200,640 Table_Name => ""List_Pragmas"");641 642 ---------------------------643 -- Ignore_Errors Feature --644 ---------------------------645 646 -- In certain cases, notably for optional subunits, the compiler operates647 -- in a mode where errors are to be ignored, and the whole unit is to be648 -- considered as not present. To implement this we provide the following649 -- flag to enable special handling, where error messages are suppressed,650 -- but the Fatal_Error flag will still be set in the normal manner.651 652 Ignore_Errors_Enable : Nat := 0;653 -- Triggering switch. If non-zero, then ignore errors mode is activated.654 -- This is a counter to allow convenient nesting of enable/disable.655 656 -----------------------657 -- CODEFIX Facility --658 -----------------------659 660 -- The GNAT Studio and GNATBench IDE's have a codefix facility that allows661 -- for automatic correction of a subset of the errors and warnings issued662 -- by the compiler. This is done by recognizing the text of specific663 -- messages using appropriate matching patterns.664 665 -- The text of such messages should not be altered without coordinating666 -- with the codefix code. All such messages are marked by a specific667 -- style of comments, as shown by the following example:668 669 -- Error_Msg_N -- CODEFIX670 -- (parameters ....)671 672 -- Any message marked with this -- CODEFIX comment should not be modified673 -- without appropriate coordination.674 675 ------------------------------676 -- Error Output Subprograms --677 ------------------------------678 679 procedure Initialize;680 -- Initializes for output of error messages. Must be called for each681 -- source file before using any of the other routines in the package.682 683 procedure Finalize (Last_Call : Boolean);684 -- Finalize processing of error message list. Includes processing for685 -- duplicated error messages, and other similar final adjustment of the686 -- list of error messages. Note that this procedure must be called before687 -- calling Compilation_Errors to determine if there were any errors. It688 -- is perfectly fine to call Finalize more than once, providing that the689 -- parameter Last_Call is set False for every call except the last call.690 691 -- This multiple call capability is used to do some processing that may692 -- generate messages. Call Finalize to eliminate duplicates and remove693 -- deleted warnings. Test for compilation errors using Compilation_Errors,694 -- then generate some more errors/warnings, call Finalize again to make695 -- sure that all duplicates in these new messages are dealt with, then696 -- finally call Output_Messages to output the final list of messages. The697 -- argument Last_Call must be set False on all calls except the last call,698 -- and must be set True on the last call (a value of True activates some699 -- processing that must only be done after all messages are posted).700 701 procedure Output_Messages;702 -- Output list of messages, including messages giving number of detected703 -- errors and warnings.704 705 procedure Error_Msg706 (Msg : String; Flag_Location : Source_Ptr);707 procedure Error_Msg708 (Msg : String; Flag_Location : Source_Ptr; N : Node_Id);709 -- Output a message at specified location. Can be called from the parser710 -- or the semantic analyzer. If N is set, points to the relevant node for711 -- this message.712 713 procedure Error_Msg714 (Msg : String;715 Flag_Location : Source_Ptr;716 Is_Compile_Time_Pragma : Boolean);717 -- Same as Error_Msg (String, Source_Ptr) except Is_Compile_Time_Pragma718 -- lets the caller specify whether this is a Compile_Time_Warning or719 -- Compile_Time_Error pragma.720 721 procedure Error_Msg_S (Msg : String);722 -- Output a message at current scan pointer location. This routine can be723 -- called only from the parser, since it references Scan_Ptr.724 725 procedure Error_Msg_AP (Msg : String);726 -- Output a message just after the previous token. This routine can be727 -- called only from the parser, since it references Prev_Token_Ptr.728 729 procedure Error_Msg_BC (Msg : String);730 -- Output a message just before the current token. Note that the important731 -- difference between this and the previous routine is that the BC case732 -- posts a flag on the current line, whereas AP can post a flag at the733 -- end of the preceding line. This routine can be called only from the734 -- parser, since it references Token_Ptr.735 736 procedure Error_Msg_SC (Msg : String);737 -- Output a message at the start of the current token, unless we are at738 -- the end of file, in which case we always output the message after the739 -- last real token in the file. This routine can be called only from the740 -- parser, since it references Token_Ptr.741 742 procedure Error_Msg_SP (Msg : String);743 -- Output a message at the start of the previous token. This routine can744 -- be called only from the parser, since it references Prev_Token_Ptr.745 746 procedure Error_Msg_N (Msg : String; N : Node_Or_Entity_Id);747 -- Output a message at the Sloc of the given node. This routine can be748 -- called from the parser or the semantic analyzer, although the call from749 -- the latter is much more common (and is the most usual way of generating750 -- error messages from the analyzer). The message text may contain a751 -- single & insertion, which will reference the given node. The message is752 -- suppressed if the node N already has a message posted, or if it is a753 -- warning and N is an entity node for which warnings are suppressed.754 755 -- WARNING: There is a matching C declaration of this subprogram in fe.h756 757 procedure Error_Msg_F (Msg : String; N : Node_Id);758 -- Similar to Error_Msg_N except that the message is placed on the first759 -- node of the construct N (First_Node (N)). Note that this procedure uses760 -- Original_Node to look at the original source tree, since that's what we761 -- want for placing an error message flag in the right place.762 763 procedure Error_Msg_NE764 (Msg : String;765 N : Node_Or_Entity_Id;766 E : Node_Or_Entity_Id);767 -- Output a message at the Sloc of the given node N, with an insertion of768 -- the name from the given entity node E. This is used by the semantic769 -- routines, where this is a common error message situation. The Msg text770 -- will contain a & or } as usual to mark the insertion point. This771 -- routine can be called from the parser or the analyzer.772 773 -- WARNING: There is a matching C declaration of this subprogram in fe.h774 775 procedure Error_Msg_FE776 (Msg : String;777 N : Node_Id;778 E : Node_Or_Entity_Id);779 -- Same as Error_Msg_NE, except that the message is placed on the first780 -- node of the construct N (First_Node (N)).781 782 procedure Error_Msg_NEL783 (Msg : String;784 N : Node_Or_Entity_Id;785 E : Node_Or_Entity_Id;786 Flag_Location : Source_Ptr);787 -- Exactly the same as Error_Msg_NE, except that the flag is placed at788 -- the specified Flag_Location instead of at Sloc (N).789 790 procedure Error_Msg_NW791 (Eflag : Boolean;792 Msg : String;793 N : Node_Or_Entity_Id);794 -- This routine is used for posting a message conditionally. The message795 -- is posted (with the same effect as Error_Msg_N (Msg, N) if and only796 -- if Eflag is True and if the node N is within the main extended source797 -- unit and comes from source. Typically this is a warning mode flag.798 -- This routine can only be called during semantic analysis. It may not799 -- be called during parsing.800 801 procedure Change_Error_Text (Error_Id : Error_Msg_Id; New_Msg : String);802 -- The error message text of the message identified by Id is replaced by803 -- the given text. This text may contain insertion characters in the804 -- usual manner, and need not be the same length as the original text.805 806 function First_Node (C : Node_Id) return Node_Id;807 -- Given a construct C, finds the first node in the construct, i.e. the one808 -- with the lowest Sloc value. This is useful in placing error msgs. Note809 -- that this procedure uses Original_Node to look at the original source810 -- tree, since that's what we want for placing an error message flag in811 -- the right place.812 813 function First_Sloc (N : Node_Id) return Source_Ptr;814 -- Given the node for an expression, return a source pointer value that815 -- points to the start of the first token in the expression. In the case816 -- where the expression is parenthesized, an attempt is made to include817 -- the parentheses (i.e. to return the location of the initial paren).818 819 function Get_Ignore_Errors return Boolean;820 -- Return True if all error calls are ignored.821 822 procedure Purge_Messages (From : Source_Ptr; To : Source_Ptr)823 renames Erroutc.Purge_Messages;824 -- All error messages whose location is in the range From .. To (not825 -- including the end points) will be deleted from the error listing.826 827 procedure Remove_Warning_Messages (N : Node_Id);828 -- Remove any warning messages corresponding to the Sloc of N or any829 -- of its descendant nodes. No effect if no such warnings. Note that830 -- style messages (identified by the fact that they start with ""(style)"")831 -- are not removed by this call. Basically the idea behind this procedure832 -- is to remove warnings about execution conditions from known dead code.833 834 procedure Remove_Warning_Messages (L : List_Id);835 -- Remove warnings on all elements of a list (Calls Remove_Warning_Messages836 -- on each element of the list, see above).837 838 procedure Reset_Warnings;839 -- Reset the counts related to warnings. This is used both to initialize840 -- these counts and to reset them after each phase of analysis for a given841 -- value of Opt.Warning_Mode in gnat2why.842 843 procedure Set_Ignore_Errors (To : Boolean);844 -- Following a call to this procedure with To=True, all error calls are845 -- ignored. A call with To=False restores the default treatment in which846 -- error calls are treated as usual (and as described in this spec).847 848 procedure Set_Warnings_Mode_Off (Loc : Source_Ptr; Reason : String_Id)849 renames Erroutc.Set_Warnings_Mode_Off;850 -- Called in response to a pragma Warnings (Off) to record the source851 -- location from which warnings are to be turned off. Reason is the852 -- Reason from the pragma, or the null string if none is given.853 854 procedure Set_Warnings_Mode_On (Loc : Source_Ptr)855 renames Erroutc.Set_Warnings_Mode_On;856 -- Called in response to a pragma Warnings (On) to record the source857 -- location from which warnings are to be turned back on.858 859 procedure Set_Specific_Warning_Off860 (Loc : Source_Ptr;861 Msg : String;862 Reason : String_Id;863 Config : Boolean;864 Used : Boolean := False)865 renames Erroutc.Set_Specific_Warning_Off;866 -- This is called in response to the two argument form of pragma Warnings867 -- where the first argument is OFF, and the second argument is a string868 -- which identifies a specific warning to be suppressed. The first argument869 -- is the start of the suppression range, and the second argument is the870 -- string from the pragma. Loc is the location of the pragma (which is the871 -- start of the range to suppress). Reason is the reason string from the872 -- pragma, or the null string if no reason is given. Config is True for the873 -- configuration pragma case (where there is no requirement for a matching874 -- OFF pragma). Used is set True to disable the check that the warning875 -- actually has the effect of suppressing a warning.876 877 procedure Set_Specific_Warning_On878 (Loc : Source_Ptr;879 Msg : String;880 Err : out Boolean)881 renames Erroutc.Set_Specific_Warning_On;882 -- This is called in response to the two argument form of pragma Warnings883 -- where the first argument is ON, and the second argument is the prefix884 -- of a specific warning to be suppressed. The first argument is the end885 -- of the suppression range, and the second argument is the string from886 -- the pragma. Err is set to True on return to report the error of no887 -- matching Warnings Off pragma preceding this one.888 889 function Compilation_Errors return Boolean;890 -- Returns True if errors have been detected, or warnings in -gnatwe (treat891 -- warnings as errors) mode. Note that it is mandatory to call Finalize892 -- before calling this routine. To account for changes to Warning_Mode in893 -- gnat2why between phases, the past or current presence of an error is894 -- recorded in a global variable at each call.895 896 procedure Error_Msg_CRT (Feature : String; N : Node_Id);897 -- Posts a non-fatal message on node N saying that the feature identified898 -- by the Feature argument is not supported in either configurable899 -- run-time mode or no run-time mode (as appropriate). In the former case,900 -- the name of the library is output if available.901 902 procedure Error_Msg_PT (E : Entity_Id; Iface_Prim : Entity_Id);903 -- Posts an error on protected type entry or subprogram E (referencing its904 -- overridden interface primitive Iface_Prim) indicating wrong mode of the905 -- first formal (RM 9.4(11.9/3)).906 907 procedure Error_Msg_Ada_2012_Feature (Feature : String; Loc : Source_Ptr);908 -- If not operating in Ada 2012 mode or higher, posts errors complaining909 -- that Feature is only supported in Ada 2012, with appropriate suggestions910 -- to fix this. Loc is the location at which the flag is to be posted.911 -- Feature, which appears at the start of the first generated message, may912 -- contain error message insertion characters in the normal manner, and in913 -- particular may start with | to flag a non-serious error.914 915 procedure Error_Msg_Ada_2020_Feature (Feature : String; Loc : Source_Ptr);916 -- Analogous to Error_Msg_Ada_2012_Feature917 918 procedure dmsg (Id : Error_Msg_Id) renames Erroutc.dmsg;919 -- Debugging routine to dump an error message920 921 ------------------------------------922 -- SPARK Error Output Subprograms --923 ------------------------------------924 925 -- The following routines are intended to report semantic errors in SPARK926 -- constructs subject to aspect/pragma SPARK_Mode. Note that syntax errors927 -- must be reported using the Error_Msg_XXX routines. This allows for the928 -- partial analysis of SPARK features when they are disabled via SPARK_Mode929 -- set to ""off"".930 931 procedure SPARK_Msg_N (Msg : String; N : Node_Or_Entity_Id);932 pragma Inline (SPARK_Msg_N);933 -- Same as Error_Msg_N, but the error is suppressed if SPARK_Mode is Off.934 -- The routine is inlined because it acts as a simple wrapper.935 936 procedure SPARK_Msg_NE937 (Msg : String;938 N : Node_Or_Entity_Id;939 E : Node_Or_Entity_Id);940 pragma Inline (SPARK_Msg_NE);941 -- Same as Error_Msg_NE, but the error is suppressed if SPARK_Mode is Off.942 -- The routine is inlined because it acts as a simple wrapper.943 944 ------------------------------------------945 -- Utility Interface for Casing Control --946 ------------------------------------------947 948 procedure Adjust_Name_Case949 (Buf : in out Bounded_String;950 Loc : Source_Ptr);951 -- Given a name stored in Buf, set proper casing. Loc is an associated952 -- source position, and if we can find a match between the name in Buf and953 -- the name at that source location, we copy the casing from the source,954 -- otherwise we set appropriate default casing.955 956 procedure Adjust_Name_Case (Loc : Source_Ptr);957 -- Uses Buf => Global_Name_Buffer. There are no calls to this in the958 -- compiler, but it is called in SPARK 2014.959 960 procedure Set_Identifier_Casing961 (Identifier_Name : System.Address;962 File_Name : System.Address);963 -- This subprogram can be used by the back end for the purposes of964 -- concocting error messages that are not output via Errout, e.g.965 -- the messages generated by the gcc back end.966 --967 -- The identifier is a null terminated string that represents the name of968 -- an identifier appearing in the source program. File_Name is a null969 -- terminated string giving the corresponding file name for the identifier970 -- as obtained from the front end by the use of Full_Debug_Name to the971 -- source file referenced by the corresponding source location value. On972 -- return, the name is in Name_Buffer, null terminated with Name_Len set.973 -- This name is the identifier name as passed, cased according to the974 -- default identifier casing for the given file.975 976 -- WARNING: There is a matching C declaration of this subprogram in fe.h977 978 function Is_Size_Too_Small_Message (S : String) return Boolean;979 Size_Too_Small_Message : constant String :=980 ""size for& too small, minimum allowed is ^"";981 -- This message is printed in Freeze and Sem_Ch13. We also test for it in982 -- the body of this package (see Special_Msg_Delete) ???which is somewhat983 -- questionable. The Is_Size_Too_Small_Message function tests for it by984 -- testing a prefix. The function and constant should be kept in synch.985 986end Errout;987",12211,False,2216.3820663738775,median988"<?xml version=""1.0"" encoding=""UTF-8"" standalone=""yes"" ?>989<!DOCTYPE boost_serialization>990<boost_serialization signature=""serialization::archive"" version=""15"">991 <syndb class_id=""0"" tracking_level=""0"" version=""0"">992 <userIPLatency>-1</userIPLatency>993 <userIPName/>994 <cdfg class_id=""1"" tracking_level=""1"" version=""0"" object_id=""_0"">995 <name>dilate_0_0_2160_3840_0_3_3_1_1_26</name>996 <ret_bitwidth>0</ret_bitwidth>997 <ports class_id=""2"" tracking_level=""0"" version=""0"">998 <count>4</count>999 <item_version>0</item_version>1000 <item class_id=""3"" tracking_level=""1"" version=""0"" object_id=""_1"">1001 <Value class_id=""4"" tracking_level=""0"" version=""0"">1002 <Obj class_id=""5"" tracking_level=""0"" version=""0"">1003 <type>1</type>1004 <id>1</id>1005 <name>imgHelper2_4102</name>1006 <fileName/>1007 <fileDirectory/>1008 <lineNumber>0</lineNumber>1009 <contextFuncName/>1010 <contextNormFuncName/>1011 <inlineStackInfo class_id=""6"" tracking_level=""0"" version=""0"">1012 <count>0</count>1013 <item_version>0</item_version>1014 </inlineStackInfo>1015 <originalName/>1016 <rtlName/>1017 <control/>1018 <opType/>1019 <implIndex/>1020 <coreName>FIFO_SRL</coreName>1021 <coreId>0</coreId>1022 </Obj>1023 <bitwidth>8</bitwidth>1024 </Value>1025 <direction>0</direction>1026 <if_type>3</if_type>1027 <array_size>0</array_size>1028 <bit_vecs class_id=""7"" tracking_level=""0"" version=""0"">1029 <count>0</count>1030 <item_version>0</item_version>1031 </bit_vecs>1032 </item>1033 <item class_id_reference=""3"" object_id=""_2"">1034 <Value>1035 <Obj>1036 <type>1</type>1037 <id>2</id>1038 <name>imgHelper3_4103</name>1039 <fileName/>1040 <fileDirectory/>1041 <lineNumber>0</lineNumber>1042 <contextFuncName/>1043 <contextNormFuncName/>1044 <inlineStackInfo>1045 <count>0</count>1046 <item_version>0</item_version>1047 </inlineStackInfo>1048 <originalName/>1049 <rtlName/>1050 <control/>1051 <opType/>1052 <implIndex/>1053 <coreName>FIFO_SRL</coreName>1054 <coreId>49</coreId>1055 </Obj>1056 <bitwidth>8</bitwidth>1057 </Value>1058 <direction>1</direction>1059 <if_type>3</if_type>1060 <array_size>0</array_size>1061 <bit_vecs>1062 <count>0</count>1063 <item_version>0</item_version>1064 </bit_vecs>1065 </item>1066 <item class_id_reference=""3"" object_id=""_3"">1067 <Value>1068 <Obj>1069 <type>1</type>1070 <id>3</id>1071 <name>p_src_rows</name>1072 <fileName/>1073 <fileDirectory/>1074 <lineNumber>0</lineNumber>1075 <contextFuncName/>1076 <contextNormFuncName/>1077 <inlineStackInfo>1078 <count>0</count>1079 <item_version>0</item_version>1080 </inlineStackInfo>1081 <originalName/>1082 <rtlName/>1083 <control/>1084 <opType/>1085 <implIndex/>1086 <coreName>FIFO_SRL</coreName>1087 <coreId>1769353058</coreId>1088 </Obj>1089 <bitwidth>32</bitwidth>1090 </Value>1091 <direction>0</direction>1092 <if_type>3</if_type>1093 <array_size>0</array_size>1094 <bit_vecs>1095 <count>0</count>1096 <item_version>0</item_version>1097 </bit_vecs>1098 </item>1099 <item class_id_reference=""3"" object_id=""_4"">1100 <Value>1101 <Obj>1102 <type>1</type>1103 <id>4</id>1104 <name>p_src_cols</name>1105 <fileName/>1106 <fileDirectory/>1107 <lineNumber>0</lineNumber>1108 <contextFuncName/>1109 <contextNormFuncName/>1110 <inlineStackInfo>1111 <count>0</count>1112 <item_version>0</item_version>1113 </inlineStackInfo>1114 <originalName/>1115 <rtlName/>1116 <control/>1117 <opType/>1118 <implIndex/>1119 <coreName>FIFO_SRL</coreName>1120 <coreId>97</coreId>1121 </Obj>1122 <bitwidth>32</bitwidth>1123 </Value>1124 <direction>0</direction>1125 <if_type>3</if_type>1126 <array_size>0</array_size>1127 <bit_vecs>1128 <count>0</count>1129 <item_version>0</item_version>1130 </bit_vecs>1131 </item>1132 </ports>1133 <nodes class_id=""8"" tracking_level=""0"" version=""0"">1134 <count>6</count>1135 <item_version>0</item_version>1136 <item class_id=""9"" tracking_level=""1"" version=""0"" object_id=""_5"">1137 <Value>1138 <Obj>1139 <type>0</type>1140 <id>11</id>1141 <name>p_src_rows_read</name>1142 <fileName>/home/willychiang/Desktop/PYNQ-HelloWorld/boards/ip/vitis_lib/vision/L1/include/imgproc/xf_dilation.hpp</fileName>1143 <fileDirectory>..</fileDirectory>1144 <lineNumber>340</lineNumber>1145 <contextFuncName>dilate&lt;0, 0, 2160, 3840, 0, 3, 3, 1, 1&gt;</contextFuncName>1146 <contextNormFuncName>dilate_0_0_2160_3840_0_3_3_1_1_s</contextNormFuncName>1147 <inlineStackInfo>1148 <count>1</count>1149 <item_version>0</item_version>1150 <item class_id=""10"" tracking_level=""0"" version=""0"">1151 <first>/home/willychiang/Desktop/PYNQ-HelloWorld/boards/ip</first>1152 <second class_id=""11"" tracking_level=""0"" version=""0"">1153 <count>1</count>1154 <item_version>0</item_version>1155 <item class_id=""12"" tracking_level=""0"" version=""0"">1156 <first class_id=""13"" tracking_level=""0"" version=""0"">1157 <first>/home/willychiang/Desktop/PYNQ-HelloWorld/boards/ip/vitis_lib/vision/L1/include/imgproc/xf_dilation.hpp</first>1158 <second>dilate&lt;0, 0, 2160, 3840, 0, 3, 3, 1, 1&gt;</second>1159 </first>1160 <second>340</second>1161 </item>1162 </second>1163 </item>1164 </inlineStackInfo>1165 <originalName/>1166 <rtlName/>1167 <control>auto</control>1168 <opType>fifo</opType>1169 <implIndex>srl</implIndex>1170 <coreName>FIFO_SRL</coreName>1171 <coreId>81</coreId>1172 </Obj>1173 <bitwidth>32</bitwidth>1174 </Value>1175 <oprand_edges>1176 <count>2</count>1177 <item_version>0</item_version>1178 <item>19</item>1179 <item>20</item>1180 </oprand_edges>1181 <opcode>read</opcode>1182 <m_Display>0</m_Display>1183 <m_isOnCriticalPath>0</m_isOnCriticalPath>1184 <m_isLCDNode>0</m_isLCDNode>1185 <m_isStartOfPath>0</m_isStartOfPath>1186 <m_delay>3.32</m_delay>1187 <m_topoIndex>1</m_topoIndex>1188 <m_clusterGroupNumber>-1</m_clusterGroupNumber>1189 </item>1190 <item class_id_reference=""9"" object_id=""_6"">1191 <Value>1192 <Obj>1193 <type>0</type>1194 <id>12</id>1195 <name>p_src_cols_read</name>1196 <fileName>/home/willychiang/Desktop/PYNQ-HelloWorld/boards/ip/vitis_lib/vision/L1/include/imgproc/xf_dilation.hpp</fileName>1197 <fileDirectory>..</fileDirectory>1198 <lineNumber>341</lineNumber>1199 <contextFuncName>dilate&lt;0, 0, 2160, 3840, 0, 3, 3, 1, 1&gt;</contextFuncName>1200 <contextNormFuncName>dilate_0_0_2160_3840_0_3_3_1_1_s</contextNormFuncName>